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-53287audit: fix incorrect inheritable capability in CAPSET records

Description

In the Linux kernel, the following vulnerability has been resolved: audit: fix incorrect inheritable capability in CAPSET records __audit_log_capset() records the effective capability set into the inheritable field due to a copy-paste error. Every CAPSET audit record therefore reports cap_pi (process inheritable) with the value of cap_effective instead of cap_inheritable. This silently corrupts audit data used for compliance and forensic analysis: an attacker who modifies inheritable capabilities to prepare for a privilege-escalating exec would have the change masked in the audit trail. The bug has been present since the original introduction of CAPSET audit records in 2008.

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

  3. · 4 months later

    Record updated

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-53287, 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.12% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 e68b75a027bb94066576139ee33676264f867b87 – < 75bd76c9eb2de9afeca03dc5152ebca5fb8fc816
    • affected e68b75a027bb94066576139ee33676264f867b87 – < febb4bf373ac565d3fb8d1f429827bdd983be496
    • affected e68b75a027bb94066576139ee33676264f867b87 – < 95de7bb4bf535a9288549d401ebde83cdcbf2792
    • affected e68b75a027bb94066576139ee33676264f867b87 – < 151ee470edc3d7ed29fe72df678f8357d2ad8ced
    • affected e68b75a027bb94066576139ee33676264f867b87 – < 0a065c51a225854768b772a0b733a44d77162582
    • affected e68b75a027bb94066576139ee33676264f867b87 – < e35f3550c5b4fab33103c18654c293cee9850b0a
    • affected e68b75a027bb94066576139ee33676264f867b87 – < d782e4d200cd9036ef353eeb29525bfbfd13a14e
    • affected e68b75a027bb94066576139ee33676264f867b87 – < e4a640475e43f406fdfd56d370b1f34b0cbbc18d
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .