CVE-2026-46104

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 25, 2026

Advisory Details (3)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

selinux: use sk blob accessor in socket permission helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d350fef4bc2467fe1bce15f7a20fe60e01ce41ad
generic

selinux: use sk blob accessor in socket permission helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7eca71f57f194c1638ebb7f4097d6be8fd04c101
generic

selinux: use sk blob accessor in socket permission helpers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/032e70aff025d7c519af9ab791cd084380619263

Vendor Advisories for CVE-2026-46104(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1—

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 05:04 UTCEG score recompute
  10. 2026-08-25 05:04 UTCVendor advisory
  11. 2026-08-25 05:03 UTCGHSA enrichment
  12. 2026-08-23 14:49 UTCEG score recompute
  13. 2026-08-23 14:49 UTCVendor advisory
  14. 2026-08-23 14:49 UTCGHSA enrichment
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 20:26 UTCEG score recompute
  18. 2026-08-21 20:26 UTCVendor advisory
  19. 2026-08-21 20:25 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 11:10 UTCEG score recompute
  22. 2026-08-20 11:10 UTCVendor advisory
  23. 2026-08-20 11:09 UTCGHSA enrichment
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-17 09:02 UTCEG score recompute
  3. 2026-08-17 09:02 UTCVendor advisory
  4. 2026-08-17 09:02 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 03:55 UTCEG score recompute
  7. 2026-08-16 03:55 UTCVendor advisory
  8. 2026-08-16 03:55 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 03:13 UTCEG score recompute
  11. 2026-08-15 03:13 UTCVendor advisory
  12. 2026-08-15 03:13 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 02:30 UTCEG score recompute
  15. 2026-08-14 02:30 UTCVendor advisory
  16. 2026-08-14 02:30 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 01:48 UTCEG score recompute
  19. 2026-08-13 01:48 UTCVendor advisory
  20. 2026-08-13 01:48 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-12 01:06 UTCEG score recompute
  23. 2026-08-12 01:06 UTCVendor advisory
  24. 2026-08-12 01:05 UTCGHSA enrichment
  25. 2026-08-11 00:21 UTCEG score recompute
  26. 2026-08-11 00:21 UTCVendor advisory
  27. 2026-08-11 00:21 UTCGHSA enrichment
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-09 23:38 UTCEG score recompute
  30. 2026-08-09 23:38 UTCVendor advisory
  31. 2026-08-09 23:38 UTCGHSA enrichment
  32. 2026-08-09 13:46 UTCEPSS rescore
  33. 2026-08-08 22:56 UTCEG score recompute
  34. 2026-08-08 22:56 UTCVendor advisory
  35. 2026-08-08 22:56 UTCGHSA enrichment
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-07 22:14 UTCEG score recompute
  38. 2026-08-07 22:14 UTCVendor advisory
  39. 2026-08-07 22:14 UTCGHSA enrichment
  40. 2026-08-06 21:31 UTCEG score recompute
  41. 2026-08-06 21:31 UTCVendor advisory
  42. 2026-08-06 21:31 UTCGHSA enrichment
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-05 20:49 UTCEG score recompute
  45. 2026-08-05 20:49 UTCVendor advisory
  46. 2026-08-05 20:49 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:39 UTCEPSS rescore
  50. 2026-08-03 16:16 UTCEG score recompute
  51. 2026-08-03 16:16 UTCVendor advisory
  52. 2026-08-03 16:16 UTCGHSA enrichment
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 15:34 UTCEG score recompute
  55. 2026-08-02 15:34 UTCVendor advisory
  56. 2026-08-02 15:34 UTCGHSA enrichment
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 14:52 UTCEG score recompute
  59. 2026-08-01 14:52 UTCVendor advisory
  60. 2026-08-01 14:52 UTCGHSA enrichment
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-31 06:48 UTCEG score recompute
  63. 2026-07-31 06:48 UTCVendor advisory
  64. 2026-07-31 06:48 UTCGHSA enrichment
  65. 2026-07-30 16:28 UTCEPSS rescore
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-29 14:35 UTCEG score recompute
  68. 2026-07-29 14:35 UTCGHSA enrichment
  69. 2026-07-28 15:36 UTCEPSS rescore
  70. 2026-07-27 14:13 UTCEPSS rescore
  71. 2026-07-27 09:51 UTCEG score recompute
  72. 2026-07-27 09:51 UTCGHSA enrichment
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-25 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46104?
CVE-2026-46104 is a medium vulnerability published on May 28, 2026. 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. sockhasperm() and nlmsgsockhasextendedperms() currently dereference sk->sk_security directly, which assumes the…
When was CVE-2026-46104 disclosed?
CVE-2026-46104 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46104 actively exploited?
CVE-2026-46104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-46104?
CVE-2026-46104 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46104?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46104, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46104

Explore →

Is Your Infrastructure Affected by CVE-2026-46104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs