CVE-2026-98419
drop_monitor: fix out-of-bounds write in reset_per_cpu_data()
No known exploitation. EPSS puts it in the 12th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 683703a26e4677db437a1480682851e27c7a154f, < caf09c09e0f323015ab6777ed1bad5aa10688631Upgrade to: caf09c09e0f323015ab6777ed1bad5aa10688631Affected: ≥ 683703a26e4677db437a1480682851e27c7a154f, < 56b12f0cd476e4d90a0e2663a80102b388ebf78cUpgrade to: 56b12f0cd476e4d90a0e2663a80102b388ebf78cAffected: ≥ 683703a26e4677db437a1480682851e27c7a154f, < 88d640efd655b10f9fa4e381caf777da1f17c2a6Upgrade to: 88d640efd655b10f9fa4e381caf777da1f17c2a6Affected: ≥ 683703a26e4677db437a1480682851e27c7a154f, < d54a044136b129822715e8798899af540ec7a9e9Upgrade to: d54a044136b129822715e8798899af540ec7a9e9 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 12th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 8 days, from the signal feeds we watch.
- OpenVAS check added
- Record updated
- Publishedrecord updated
Affected products
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI