Linux · Rocky Linux · Security advisory · November 7, 2026

RLSA-2026:95367: kernel security update

RLSA-2026:95367, released November 7, 2026, fixes 8 CVEs in kernel (version 0:6.12.0-211.74.1.el10_2). None of them is reported as exploited. Patch Radar priority: Urgent.

Urgent
CVEs closed
8
2 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0064
50th percentile

Priority of the 8 CVEs

Patch now 0 Urgent 2 High 6 Routine 0

Fixed package versions

ProductReleaseFixed in
kernelrocky 100:6.12.0-211.74.1.el10_2

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Urgent CVE-2026-72221 linux: In the Linux kernel, the following vulnerability has been resolved: sunrpc: wait for in-flight TLS handshake callbac...9.8 0.0064 None reported
Urgent CVE-2026-72222 linux: In the Linux kernel, the following vulnerability has been resolved: sunrpc: pin svc_xprt across the asynchronous TLS...9.8 0.0064 None reported
High CVE-2026-74586 sctp: clear new_transport when removing a peer9.8 0.0050 None reported
High CVE-2026-90315 linux: In the Linux kernel, the following vulnerability has been resolved: PCI/sysfs: Add lockdown checks to legacy I/O and...8.8 0.0020 None reported
High CVE-2026-72080 linux: In the Linux kernel, the following vulnerability has been resolved: fs/resctrl: Fix use-after-free during unmount D...8.8 0.0017 None reported
High CVE-2026-98974 linux: In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range-to-eof file size exchang...8.8 0.0016 None reported
High CVE-2026-89488 linux: In the Linux kernel, the following vulnerability has been resolved: openvswitch: Fix CT limit teardown use-after-fre...8.8 0.0013 None reported
High CVE-2026-64378 writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs()8.8 0.0010 None reported
Showing 1 to 8 of 8 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.