CVE-2026-53295 | mailbox: add sanity check for channel array

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.

Published: 2026-06-26 Last update: 2026-07-07 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-53295 is rated Low Risk (22.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.12%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-53295

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-08 0.18% 0.12% -0.05%
2 2026-06-27 — 0.18% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-53295

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2026-53295

GitHub Security Advisory for CVE-2026-53295

GHSA-rf57-3w24-v5g9 · Severity: medium — In the Linux kernel, the following vulnerability has been resolved: mailbox: add sanity check...

OS Trackers for CVE-2026-53295

vendor priority summary link
debian not yet assigned CVE-2026-53295 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2026-53295
suse — — https://www.suse.com/security/cve/CVE-2026-53295/
ubuntu medium CVE-2026-53295 medium priority: Ubuntu including 162 source packages (linux, linux-allwinner-5.19, …), 1458 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 1051, ignored 175, needed 93, released 88, pending 49, needs-triage 1, not-affected 1. https://ubuntu.com/security/CVE-2026-53295

Affected software / configurations for CVE-2026-53295

Vendor Product Version Raw CPE
linux linux_kernel >= 3.18.1, < 5.10.258 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.209 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.175 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.6.141 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.7, < 6.12.91 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.13, < 6.18.33 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.19, < 7.0.10 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 3.18 cpe:2.3:o:linux:linux_kernel:3.18:-:*:*:*:*:*:*
linux linux_kernel 3.18 cpe:2.3:o:linux:linux_kernel:3.18:rc2:*:*:*:*:*:*
linux linux_kernel 3.18 cpe:2.3:o:linux:linux_kernel:3.18:rc3:*:*:*:*:*:*
linux linux_kernel 3.18 cpe:2.3:o:linux:linux_kernel:3.18:rc4:*:*:*:*:*:*
linux linux_kernel 3.18 cpe:2.3:o:linux:linux_kernel:3.18:rc5:*:*:*:*:*:*
linux linux_kernel 3.18 cpe:2.3:o:linux:linux_kernel:3.18:rc6:*:*:*:*:*:*
linux linux_kernel 3.18 cpe:2.3:o:linux:linux_kernel:3.18:rc7:*:*:*:*:*:*
linux linux_kernel 7.1 cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*

References for CVE-2026-53295

cvelogic Threat Intelligence