cve.bz

CVE-2025-68299 linux linux

no score yetEPSS 0.3%

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

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2025-68299

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68299](https://cve.bz/cve/badge/CVE-2025-68299.svg)](https://cve.bz/cve/CVE-2025-68299)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68299"><img src="https://cve.bz/cve/badge/CVE-2025-68299.svg" alt="CVE-2025-68299"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 6.17.9 before 6.17.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux6.17.11-1DEBIAN-CVE-2025-68299
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68299
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68299
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68299
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-68299
Ubuntu24.04:LTSlinux-aws-6.176.17.0-1009.9~24.04.2UBUNTU-CVE-2025-68299 USN-8094-1
Ubuntu24.04:LTSlinux-azure-6.176.17.0-1010.10~24.04.1UBUNTU-CVE-2025-68299 USN-8094-4
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1009.9~24.04.3UBUNTU-CVE-2025-68299 USN-8094-2
Ubuntu24.04:LTSlinux-hwe-6.176.17.0-19.19~24.04.2UBUNTU-CVE-2025-68299 USN-8094-1
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1017.17UBUNTU-CVE-2025-68299 USN-8152-1
Ubuntu24.04:LTSlinux-oracle-6.176.17.0-1009.9~24.04.1UBUNTU-CVE-2025-68299 USN-8094-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-gcp-6.11 and 8 moreno fix listedUBUNTU-CVE-2025-68299
Ubuntu24.04:LTSlinux-riscv-6.176.17.0-19.19.1~24.04.1UBUNTU-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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix 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.

References

Check your stackJSON