CVE-2026-63800
What it is
In the Linux kernel, the following vulnerability has been resolved: pNFS: Fix use-after-free in pnfs_update_layout() When hitting the NFS_LAYOUT_RETURN branch in pnfs_update_layout(), the code calls pnfs_prepare_to_retry_layoutget(lo). If it succeeds, pnfs_put_layout_hdr(lo) is called before trace_pnfs_update_layout(), which still references 'lo'. This results in a use-after-free when the tracepoint accesses lo's fields. Fix this by moving the tracepoint call before pnfs_put_layout_hdr(lo).
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.6% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.6% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 5.5
- Linux Kernel < 5.10.260
- Linux Kernel < 5.15.211
- Linux Kernel < 6.1.177
- Linux Kernel < 6.6.144
- Linux Kernel < 6.12.95
- Linux Kernel < 6.18.38
- Linux Kernel < 7.1.3
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-63800.md and follow it. Check whether this project is affected by CVE-2026-63800. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/13e198a90ca4050f4bee8a3f23680389a6563ccc
- https://git.kernel.org/stable/c/1f24b8302c77dcaf79c64c073877a3b9f4dd25d2
- https://git.kernel.org/stable/c/200e7637f4d6a1342987045eea72641524f909dc
- https://git.kernel.org/stable/c/2883ddd7542b4437a2ab4908fe2773f690e20889
- https://git.kernel.org/stable/c/4ad8b9a85dbf57ca532ee9e65ad7e6498bfbbf98
- https://git.kernel.org/stable/c/7e37e9b3e82ade881e1798e2f4fcc54aff7793c1
- https://git.kernel.org/stable/c/9645aaf689aff57427ece3b9fa47d5b5399417f4
- https://git.kernel.org/stable/c/9c0fb5c09ae5bd68dc0038692af8127029cb0385
References
- https://git.kernel.org/stable/c/13e198a90ca4050f4bee8a3f23680389a6563ccc
- https://git.kernel.org/stable/c/1f24b8302c77dcaf79c64c073877a3b9f4dd25d2
- https://git.kernel.org/stable/c/200e7637f4d6a1342987045eea72641524f909dc
- https://git.kernel.org/stable/c/2883ddd7542b4437a2ab4908fe2773f690e20889
- https://git.kernel.org/stable/c/4ad8b9a85dbf57ca532ee9e65ad7e6498bfbbf98
- https://git.kernel.org/stable/c/7e37e9b3e82ade881e1798e2f4fcc54aff7793c1
- https://git.kernel.org/stable/c/9645aaf689aff57427ece3b9fa47d5b5399417f4
- https://git.kernel.org/stable/c/9c0fb5c09ae5bd68dc0038692af8127029cb0385