Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-45848apparmor: fix NULL sock in aa_sock_file_perm

Description

In the Linux kernel, the following vulnerability has been resolved: apparmor: fix NULL sock in aa_sock_file_perm Deal with the potential that sock and sock-sk can be NULL during socket setup or teardown. This could lead to an oops. The fix for NULL pointer dereference in __unix_needs_revalidation shows this is at least possible for af_unix sockets. While the fix for af_unix sockets applies for newer mediation this is still the fall back path for older af_unix mediation and other sockets, so ensure it is covered.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-45848, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < 68538ec34fcb4194c7961dc4eca6f5537fec8067
    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < 5121b7283f1c46e4c06b88b1dda7b064429d77de
    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < c11b7c3280d000376e27ebfed17ec7046699eab4
    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < 0dc19bca22606f7a61d5988408f74e3ae0ef3486
    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < 3852eb9a0392eb435c03dcb47d581bcfe6a9a95b
    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < ccb66a3c6c8f51b3ed1bc003b70bb9ff99e8d835
    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < 8a0ededbfcff74598f82f1d4b8ef9db28878b317
    • affected 56974a6fcfef69ee0825bd66ed13e92070ac5224 – < 00b67657535dfea56e84d11492f5c0f61d0af297
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.14 – ≤ 6.18.*
    • unaffected 6.19.4 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-45848 badge
[![CVE-2026-45848](https://cveledger.app/badge/CVE-2026-45848.svg)](https://cveledger.app/cve/CVE-2026-45848)

Record last updated .