Look up another CVE · open CVE-2026-68473 in the interactive tracker
CVE-2026-68473
powerpc/uaccess: correct check for CONFIG_PPC_E500 in mask_user_address()
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem arch/powerpc. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-68473 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
mask_user_address() incorrectly checks for CONFIG_E500 instead of CONFIG_PPC_E500, causing mask_user_address_isel() to not be used on E500 hardware. Fix the check to use the correct name.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
arch/powerpc/include/asm/uaccess.h
- What this is
- LINUX FOR POWERPC (32-BIT AND 64-BIT)MAINTAINERS section matched on arch/powerpc/ · linuxppc-dev@lists.ozlabs.org · Supported
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.4% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- arch/powerpc
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 7.0 | 7.1.5 | d5c234774a82 |
| 7.0 | 7.2 | d610d3ab1819 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- Exploitation requires invoking local syscalls (read/write/ioctl/futex/socket) that reach masked uaccess helpers; the bug is in arch/powerpc uaccess.h and is not triggered by remote packet handling alone.
- AC:LAttack complexity, low
- On affected PPC_E500 kernels (7.0+), any user pointer with bit 31 set reliably redirects to 0x80000000 on masked copy/futex paths without races or rare layout wins.
- PR:LPrivileges required, low
- Any unprivileged local process can pass crafted userspace pointers into copy_from_user, strncpy_from_user, iov_iter, futex_wake_op, and scoped socket/scm helpers that use masked_user_access_begin.
- UI:NUser interaction, none
- No victim interaction is required; exploitation is achieved entirely through attacker-controlled syscall arguments and memory mappings.
- S:UScope, unchanged
- Impact is confined to kernel/user memory boundaries on the same host (cross-process read/write via misdirected uaccess), not a hypervisor or separate security authority escape.
- C:HConfidentiality impact, high
- Wrong masking lets masked copy_from_user/strncpy_from_user read from 0x80000000 instead of the supplied high user or kernel-range pointer, enabling kernel-mediated disclosure of other mappings at that fixed address.
- I:HIntegrity impact, high
- Masked futex atomic ops and scoped user writes on mis-masked pointers can modify memory at 0x80000000 rather than the validated target, corrupting synchronization state or arbitrary user data.
- A:HAvailability impact, high
- Misdirected user accesses can trigger KUAP/KUEP faults, WARN paths, or persistent futex corruption, causing kernel oops/panics or denial of service on embedded E500 systems.