CVE-2026-72378 json
afs: Fix error code in afs_extract_vl_addrs()
published 2mo ago modified 2mo ago also EUVD-2026-59277
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix error code in afs_extract_vl_addrs()
The error codes on these paths are only set on the first iteration through the loop. Set the correct error code on every iteration.
Patch / fix
- Linux Linux 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.5-1
debian advisories DEBIAN-CVE-2026-72378
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-72378
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/7ce6737a975ea3e0dc2e5946628d233779ca0caf commit
- git.kernel.org/stable/c/4e0b047848a855f2c933a6439f76a01743ba5620 commit
- git.kernel.org/stable/c/f70fbf2b974b63a7042705c2b0464cb8c97e9f34 commit
- git.kernel.org/stable/c/9ad9016e3333c3c1f9284a253ff0658369e07aac commit
- git.kernel.org/stable/c/cb33dd2968588c78fad78dec19f61cabe5785494 commit
- git.kernel.org/stable/c/8530206911fd66ad739ca5ce95f1d069f3d42204 commit
- git.kernel.org/stable/c/bdcd80ff12939d172043fac5eb822b92366a1bab commit
- git.kernel.org/stable/c/4897cb71d4ab1f7e1a214adb1e4b80176702368d commit
Is CVE-2026-72378 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-72378 updated cvss 5.5
kernel: afs: Fix error code in afs_extract_vl_addrs()
-
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 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 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
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/7ce6737a975ea3e0dc2e5946628d233779ca0caf
- git.kernel.org /stable/c/4e0b047848a855f2c933a6439f76a01743ba5620
- git.kernel.org /stable/c/f70fbf2b974b63a7042705c2b0464cb8c97e9f34
- git.kernel.org /stable/c/9ad9016e3333c3c1f9284a253ff0658369e07aac
- git.kernel.org /stable/c/cb33dd2968588c78fad78dec19f61cabe5785494
- git.kernel.org /stable/c/8530206911fd66ad739ca5ce95f1d069f3d42204
- git.kernel.org /stable/c/bdcd80ff12939d172043fac5eb822b92366a1bab
- git.kernel.org /stable/c/4897cb71d4ab1f7e1a214adb1e4b80176702368d
Sources
- CVE List CVE-2026-72378
- NVD CVE-2026-72378
Fencer Intel 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.