selinux: use sk blob accessor in socket permission helpers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 032e70aff025d7c519af9ab791cd084380619263, Kernel 7eca71f57f194c1638ebb7f4097d6be8fd04c101 and Kernel d350fef4bc2467fe1bce15f7a20fe60e01ce41ad.
In the Linux kernel, the following vulnerability has been resolved: selinux: use sk blob accessor in socket permission helpers SELinux socket state lives in the composite LSM socket blob. sock_has_perm() and nlmsg_sock_has_extended_perms() currently dereference sk->sk_security directly, which assumes the SELinux socket blob is at offset zero. In stacked configurations that assumption does not hold. If another LSM allocates socket blob storage before SELinux, these helpers may read the wrong blob and feed invalid SID and class values into AVC checks. Use selinux_sock() instead of accessing sk->sk_security directly.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.13, >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <032e70aff025d7c519af9ab791cd084380619263, >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <7eca71f57f194c1638ebb7f4097d6be8fd04c101, >=d1d991efaf34606d500dcbd28bedc0666eeec8e2 <d350fef4bc2467fe1bce15f7a20fe60e01ce41ad | 032e70aff025d7c519af9ab791cd084380619263, 7eca71f57f194c1638ebb7f4097d6be8fd04c101, d350fef4bc2467fe1bce15f7a20fe60e01ce41ad |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket