Answer in brief
CVE-2026-98419 records a High severity (CVSS 7.0) vulnerability in drop_monitor: fix out-of-bounds write in reset_per_cpu_data(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=683703a26e4677db437a1480682851e27c7a154f <caf09c09e0f323015ab6777ed1bad5aa10688631 || >=683703a26e4677db437a1480682851e27c7a154f <56b12f0cd476e4d90a0e2663a80102b388ebf78c || >=683703a26e4677db437a1480682851e27c7a154f <88d640efd655b10f9fa4e381caf777da1f17c2a6 || >=683703a26e4677db437a1480682851e27c7a154f <d54a044136b129822715e8798899af540ec7a9e9 || >=683703a26e4677db437a1480682851e27c7a154f <8a04047c6dbff2f49a561b1ff53b043f4807e855 || >=683703a26e4677db437a1480682851e27c7a154f <530ae0a1458078c7a81fbffd9ff17d42129364d9 || >=683703a26e4677db437a1480682851e27c7a154f <03b672eba4937ff18337049824a114012d57f202 || >=683703a26e4677db437a1480682851e27c7a154f <439f392084f8f7f59ab9d47a9579185accefe1d8 | caf09c09e0f323015ab6777ed1bad5aa10688631, 56b12f0cd476e4d90a0e2663a80102b388ebf78c, 88d640efd655b10f9fa4e381caf777da1f17c2a6, d54a044136b129822715e8798899af540ec7a9e9, 8a04047c6dbff2f49a561b1ff53b043f4807e855, 530ae0a1458078c7a81fbffd9ff17d42129364d9, 03b672eba4937ff18337049824a114012d57f202, 439f392084f8f7f59ab9d47a9579185accefe1d8 |
| Linux/Linuxgeneric | 2.6.31 | Not reported |
Published upstream
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.