Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98419: drop_monitor: fix out-of-bounds write in reset_per_cpu_data()

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 03b672eba4937ff18337049824a114012d57f202, 439f392084f8f7f59ab9d47a9579185accefe1d8, 530ae0a1458078c7a81fbffd9ff17d42129364d9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 03b672eba4937ff18337049824a114012d57f202, 439f392084f8f7f59ab9d47a9579185accefe1d8, 530ae0a1458078c7a81fbffd9ff17d42129364d9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: drop_monitor: fix out-of-bounds write in reset_per_cpu_data() In reset_per_cpu_data(), al is computed as: al = sizeof(struct net_dm_alert_msg); al += dm_hit_limit * sizeof(struct net_dm_drop_point); al += sizeof(struct nlattr); skb = genlmsg_new(al, GFP_KERNEL); ... nla = nla_reserve(skb, NLA_UNSPEC, sizeof(struct net_dm_alert_msg)); ... msg = nla_data(nla); memset(msg, 0, al); Because al includes sizeof(struct nlattr) (the 4-byte attribute header), genlmsg_new() allocates al bytes of tailroom starting at nla. However, msg points to nla_data(nla), which is located sizeof(struct nlattr) bytes past nla. Calling memset(msg, 0, al) therefore writes al bytes starting from msg, exceeding the allocated buffer by sizeof(struct nlattr) (4 bytes) and corrupting skb_shared_info. Fix this by letting al represent only the payload length, allocating the skb with genlmsg_new(nla_total_size(al), GFP_KERNEL), and zeroing al bytes from msg.

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Oct 14, 2026
Updated
Oct 24, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98419

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.31affected
    • 683703a26e4677db437a1480682851e27c7a154f and later · before caf09c09e0f323015ab6777ed1bad5aa10688631affected · git
    • 683703a26e4677db437a1480682851e27c7a154f and later · before 56b12f0cd476e4d90a0e2663a80102b388ebf78caffected · git
    • 683703a26e4677db437a1480682851e27c7a154f and later · before 88d640efd655b10f9fa4e381caf777da1f17c2a6affected · git
    • 683703a26e4677db437a1480682851e27c7a154f and later · before d54a044136b129822715e8798899af540ec7a9e9affected · git
    • 683703a26e4677db437a1480682851e27c7a154f and later · before 8a04047c6dbff2f49a561b1ff53b043f4807e855affected · git
    • 683703a26e4677db437a1480682851e27c7a154f and later · before 530ae0a1458078c7a81fbffd9ff17d42129364d9affected · git
    • 683703a26e4677db437a1480682851e27c7a154f and later · before 03b672eba4937ff18337049824a114012d57f202affected · git
    • 683703a26e4677db437a1480682851e27c7a154f and later · before 439f392084f8f7f59ab9d47a9579185accefe1d8affected · git
    • before 2.6.31not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.8-17.2.8-1
openSUSE:Tumbleweedkernel-sourcebefore 7.2.11-1.17.2.11-1.1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98417Oct 14, 2026 · net: xfrm: reject unrepresentable espintcp transport headers
    0Monitor
  • ← EarlierCVE-2026-98418Oct 14, 2026 · sched/core: Avoid false migration warning for proxy donors
    0Monitor
  • Later →CVE-2026-98420Oct 14, 2026 · ksmbd: follow SMB2 session expiration semantics
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux03b672eba4937ff18337049824a114012d57f202Vendor (CNA)
Linux Linux439f392084f8f7f59ab9d47a9579185accefe1d8Vendor (CNA)
Linux Linux530ae0a1458078c7a81fbffd9ff17d42129364d9Vendor (CNA)
Linux Linux56b12f0cd476e4d90a0e2663a80102b388ebf78cVendor (CNA)
Linux Linux88d640efd655b10f9fa4e381caf777da1f17c2a6Vendor (CNA)
Linux Linux8a04047c6dbff2f49a561b1ff53b043f4807e855Vendor (CNA)
Linux Linuxcaf09c09e0f323015ab6777ed1bad5aa10688631Vendor (CNA)
Linux Linuxd54a044136b129822715e8798899af540ec7a9e9Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.159.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.2.11-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 6, 2026+23 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. CVSS— → 7
  2. Severity— → high
  3. Exploit maturity— → none
  4. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records