CVE-2026-53296 json
mailbox: mailbox-test: free channels on probe error
published 2026-06-26 4 mo ago modified 2026-11-06 2 d ago also EUVD-2026-39901
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
mailbox: mailbox-test: free channels on probe error
On probe error, free the previously obtained channels. This not only prevents a leak, but also UAF scenarios because the client structure will be removed nonetheless because it was allocated with devm.
Patch / fix
- Linux Linux 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.10-1
debian advisories DEBIAN-CVE-2026-53296
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
ubuntu advisories UBUNTU-CVE-2026-53296
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/0ad8c4a03a358de7811ba1ab8cbd1fe76ad0ff6b commit
- git.kernel.org/stable/c/15c4cc3850cfe1b973eb7b63c02314b267f06a64 commit
- git.kernel.org/stable/c/187069ccc3474516af32350e20d7e449160fa6de commit
- git.kernel.org/stable/c/81c9e7e4030e71391ab479c4c6e17b64802577aa commit
- git.kernel.org/stable/c/6c6ce2ccb4fcf1617fec83f91b21aa0265f30701 commit
- git.kernel.org/stable/c/742001919653e7313b4e91780c5d108be1692365 commit
- git.kernel.org/stable/c/02beb178e2e159daeb8f992d7abb16a37da31664 commit
- git.kernel.org/stable/c/c02053a9055d5fdfd32432287cca8958db1d5bc5 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-53296 updated cvss 4.7
kernel: mailbox: mailbox-test: free channels on probe error
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/0ad8c4a03a358de7811ba1ab8cbd1fe76ad0ff6b
patch
-
git.kernel.org
/stable/c/15c4cc3850cfe1b973eb7b63c02314b267f06a64
patch
-
git.kernel.org
/stable/c/187069ccc3474516af32350e20d7e449160fa6de
patch
-
git.kernel.org
/stable/c/81c9e7e4030e71391ab479c4c6e17b64802577aa
patch
-
git.kernel.org
/stable/c/6c6ce2ccb4fcf1617fec83f91b21aa0265f30701
patch
-
git.kernel.org
/stable/c/742001919653e7313b4e91780c5d108be1692365
patch
-
git.kernel.org
/stable/c/02beb178e2e159daeb8f992d7abb16a37da31664
patch
-
git.kernel.org
/stable/c/c02053a9055d5fdfd32432287cca8958db1d5bc5
patch
Sources
- CVE List CVE-2026-53296
- NVD CVE-2026-53296
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.