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-53295mailbox: add sanity check for channel array

Description

In the Linux kernel, the following vulnerability has been resolved: mailbox: add sanity check for channel array Fail gracefully if there is no channel array attached to the mailbox controller. Otherwise the later dereference will cause an OOPS which might not be seen because mailbox controllers might instantiate very early. Remove the comment explaining the obvious while here.

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

  3. · 5 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-53295, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.13% · top 97% of all CVEs (15 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 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < 5cc3300fab262b26c28bc2fc06df693410c3840b
    • affected 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < 0f11444271110d9b5bc6316a153c6431abda899c
    • affected 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < d44872a569b8fbacde457ff2587a775e5004bb79
    • affected 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < 14aed0d4e58389cc6a88acf8610b12d3e476272b
    • affected 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < 6362c4a7d7e21e68cd9aa04df7cde16befba3a4b
    • affected 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < 9dd7489943324298bb0f385495795a82f1dd6507
    • affected 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < 37792091ab28ba030fd8d61184c47d4d51294170
    • affected 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c – < c1aad75595fb67edc7fda8af249d3b886efa1be9
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • 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

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .