CVE-2025-68299 linux linux
linux linux: no CVSS score yet. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix delayed allocation of a cell's anonymous key
The allocation of a cell's anonymous key is done in a background thread
along with other cell setup such as doing a DNS upcall. In the reported
bug, this is triggered by afs_parse_source() parsing the device name given
to mount() and calling afs_lookup_cell() with the name of the cell.
The normal key lookup then tries to use the key description on the
anonymous authentication key as the reference for request_key() - but it
may not yet be set and so an oops can happen.
This has been made more likely to happen by the fix for dynamic lookup
failure.
Fix this by firstly allocating a reference name and attaching it to the
afs_cell record when the record is created. It can share the memory
allocation with the cell name (unfortunately it can't just overlap the cell
name by prepending it with "afs@" as the cell name already has a '.'
prepended for other purposes). This reference name is then passed to
request_key().
Secondly, the anon key is now allocated on demand at the point a key is
requested in afs_request_key() if it is not already allocated. A mutex is
used to prevent multiple allocation for a cell.
Thirdly, make afs_request_key_rcu() return NULL if the anonymous key isn't
yet allocated (if we need it) and then the caller can return -ECHILD to
drop out of RCU-mode and afs_request_key() can be called.
Note that the anonymous key is kind of necessary to make the key lookup
cache work as that doesn't currently cache a negative lookup, but it's
probably worth some investigation to see if NULL can be used instead.
- EPSS
- 0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Fix and patched versions
- Debian, Ubuntu: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2025-68299 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68299?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68299?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68299 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | from 6.17.9 before 6.17.11 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 6.17.11-1 | DEBIAN-CVE-2025-68299 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2025-68299 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2025-68299 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2025-68299 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2025-68299 |
| Ubuntu | 24.04:LTS | linux-aws-6.17 | 6.17.0-1009.9~24.04.2 | UBUNTU-CVE-2025-68299 USN-8094-1 |
| Ubuntu | 24.04:LTS | linux-azure-6.17 | 6.17.0-1010.10~24.04.1 | UBUNTU-CVE-2025-68299 USN-8094-4 |
| Ubuntu | 24.04:LTS | linux-gcp-6.17 | 6.17.0-1009.9~24.04.3 | UBUNTU-CVE-2025-68299 USN-8094-2 |
| Ubuntu | 24.04:LTS | linux-hwe-6.17 | 6.17.0-19.19~24.04.2 | UBUNTU-CVE-2025-68299 USN-8094-1 |
| Ubuntu | 24.04:LTS | linux-oem-6.17 | 6.17.0-1017.17 | UBUNTU-CVE-2025-68299 USN-8152-1 |
| Ubuntu | 24.04:LTS | linux-oracle-6.17 | 6.17.0-1009.9~24.04.1 | UBUNTU-CVE-2025-68299 USN-8094-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-gcp-6.11 and 8 more | no fix listed | UBUNTU-CVE-2025-68299 |
| Ubuntu | 24.04:LTS | linux-riscv-6.17 | 6.17.0-19.19.1~24.04.1 | UBUNTU-CVE-2025-68299 |
| 6 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat
Red Hat rates this Moderate.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68299.