Skip to main content
VulnerabilityPublished Updated

CVE-2026-53295: Linux kernel · mailbox: add sanity check for channel array

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d44872a569b8fbacde457ff2587a775e5004bb79 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in d44872a569b8fbacde457ff2587a775e5004bb79, c1aad75595fb67edc7fda8af249d3b886efa1be9, 37792091ab28ba030fd8d61184c47d4d51294170 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c, < d44872a569b8fbacde457ff2587a775e5004bb79
Fixed in
  • d44872a569b8fbacde457ff2587a775e5004bb79
LinuxLinuxAffected
  • ≥ 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c, < c1aad75595fb67edc7fda8af249d3b886efa1be9
Fixed in
  • c1aad75595fb67edc7fda8af249d3b886efa1be9
LinuxLinuxAffected
  • ≥ 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c, < 37792091ab28ba030fd8d61184c47d4d51294170
Fixed in
  • 37792091ab28ba030fd8d61184c47d4d51294170
LinuxLinuxAffected
  • ≥ 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c, < 6362c4a7d7e21e68cd9aa04df7cde16befba3a4b
Fixed in
  • 6362c4a7d7e21e68cd9aa04df7cde16befba3a4b
LinuxLinuxAffected
  • ≥ 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c, < 14aed0d4e58389cc6a88acf8610b12d3e476272b
Fixed in
  • 14aed0d4e58389cc6a88acf8610b12d3e476272b
LinuxLinuxAffected
  • ≥ 2b6d83e2b8b7de82331a6a1dcd64b51020a6031c, < 9dd7489943324298bb0f385495795a82f1dd6507
Fixed in
  • 9dd7489943324298bb0f385495795a82f1dd6507

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.

References

Community reviews

Loading reviews…