CVE-2026-98899 — netfilter: ipset: mark the rcu locked areas properly
In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: mark the rcu locked areas properly When we bump the uref counter, there's no need to keep the rcu lock because the referred hash table can't disappear. Also, from the same reason in mtype_gc we need the rcu lock and not a spinlock.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 67bd3d2350d17c2f4fb158c3f917c10b15ecbc94≥ f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 892399abd1a005a455d5b74d86d82b9773405f2b≥ f66ee0410b1c3481ee75e5db9b34547b4d582465 and < eee5172741b2c0e73210020732043e5d589295d3≥ f66ee0410b1c3481ee75e5db9b34547b4d582465 and < ecb48c6b9edc78de8dd456c365727ae14b88c1ee≥ f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 0c46c9ce24130657ec7460c27fba5d445f5abd06≥ f66ee0410b1c3481ee75e5db9b34547b4d582465 and < ca9fab1ca15534cef1630e81a479e94b3bbcdb6a≥ f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 5d0c22e73656d050daffad10a2ba8765ce8441c8version 5dd9488ae41070b69d2f4acb580f77db5705f9ca and 4 moreversion a469bab3386aebff33c59506f3a95e35b91118fd≥ 5.4.24 and < 5.5≥ 5.5.8 and < 5.6version 5.6 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products removed · 14
- Affected products added · linux/linux
- CVSS changed · 7.8
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 23, 2026 – Oct 24, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
9 on the record
- nvd.nist.gov/vuln/detail/CVE-2026-98899
- github.com/advisories/GHSA-ffrw-gp84-hx8m
- git.kernel.org/stable/c/ecb48c6b9edc78de8dd456c365727ae14b88c1ee
- git.kernel.org/stable/c/5d0c22e73656d050daffad10a2ba8765ce8441c8
- git.kernel.org/stable/c/ca9fab1ca15534cef1630e81a479e94b3bbcdb6a
- git.kernel.org/stable/c/67bd3d2350d17c2f4fb158c3f917c10b15ecbc94
- git.kernel.org/stable/c/eee5172741b2c0e73210020732043e5d589295d3
- git.kernel.org/stable/c/0c46c9ce24130657ec7460c27fba5d445f5abd06
- git.kernel.org/stable/c/892399abd1a005a455d5b74d86d82b9773405f2b
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98899 is "netfilter: ipset: mark the rcu locked areas properly", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.