CVE-2026-98854 json
of/overlay: only treat a positive changeset id as registered
published 2026-10-18 21 d ago modified 2026-10-30 9 d ago also EUVD-2026-103794
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
of/overlay: only treat a positive changeset id as registered
of_overlay_fdt_apply() stores the idr_alloc() return value in ovcs->id before checking it. On failure the stored id is negative, free_overlay_changeset()'s "if (ovcs->id)" check passes, idr_remove() is called with a negative id and list_del() runs on ovcs->ovcs_list, which is not initialized until after the id allocation. An allocation failure at that point dereferences NULL.
Make free_overlay_changeset() treat only a strict-positive id as registered. The rest of the function already copes with a partially-initialized ovcs, so the error path stays a plain goto err_free_ovcs.
Patch / fix
- Linux Linux 5.15.224, 6.1.191, 6.6.160, 6.12.113, 6.18.56, 7.2.10, 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.10-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98854
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-109332
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/7af5d66d0514b8f1d759d0e32b9d4c5d26263e4a commit
- git.kernel.org/stable/c/71065f3d6864a101b77e7af84566757c4df415a0 commit
- git.kernel.org/stable/c/cc688475c56d34a2b584141f9544cbe23360080d commit
- git.kernel.org/stable/c/c08a54df9d33dcd6ff089adc9434b2c008af3a39 commit
- git.kernel.org/stable/c/0d1525fdcd3355672b7485d61e55df6824ab5ad1 commit
- git.kernel.org/stable/c/c875407c34dadaef0599834ad9c815f4c9f50d15 commit
- git.kernel.org/stable/c/44081d708b5b885487bac792db78324b7b4c267d commit
Vendor 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-98854 updated cvss 4.1
kernel: of/overlay: only treat a positive changeset id as registered
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8affected: 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 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not 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.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/7af5d66d0514b8f1d759d0e32b9d4c5d26263e4a
- git.kernel.org /stable/c/71065f3d6864a101b77e7af84566757c4df415a0
- git.kernel.org /stable/c/cc688475c56d34a2b584141f9544cbe23360080d
- git.kernel.org /stable/c/c08a54df9d33dcd6ff089adc9434b2c008af3a39
- git.kernel.org /stable/c/0d1525fdcd3355672b7485d61e55df6824ab5ad1
- git.kernel.org /stable/c/c875407c34dadaef0599834ad9c815f4c9f50d15
- git.kernel.org /stable/c/44081d708b5b885487bac792db78324b7b4c267d
Sources
- CVE List CVE-2026-98854
- NVD CVE-2026-98854
Fencer Vulns 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.