drop_monitor: fix out-of-bounds write in reset_per_cpu_data()
Assessment
- Severity
- Moderate
- CVSS base score
- 5.1CVSS:3.1/
AV:L/ AC:L/ PR:H/ UI:N/ S:U/ C:N/ I:L/ A:H - Impact
- Not stated
- EPSS, next 30 days
- Not scored yet
- Public exploit code
- No Nuclei template lists it
- Exploitability
- Not assessed
- Publicly disclosed
- No
- Customer action
- Required: apply the update
- Component
- Mariner
- Weakness
- —
- Issued by
- Linux
- Published
- 16 Oct 2026 · October 2026
- Last revised
- 24 Oct 2026Information published.
- Attack vector
- LocalAV:L
- Attack complexity
- LowAC:L
- Privileges required
- HighPR:H
- User interaction
- NoneUI:N
- Scope
- UnchangedS:U
- Confidentiality
- NoneC:N
- Integrity
- LowI:L
- Availability
- HighA:H
Updates that fix it
0 KBsNo KB listed
MSRC lists no downloadable update, which usually means a service-side fix or a release-notes update. Check the MSRC advisory.
Affected products
1 affected product
- azl3 kernel 6.6.157.1-1 on Azure Linux 3.0
What changed
First observed 16 Oct 2026- 25 Oct 2026 · 07:41:18 UTC Last revised21 Oct 2026 18:42 UTC → 24 Oct 2026 14:49 UTC
- 23 Oct 2026 · 09:33:49 UTC Public exploit codeUnknown: exploit-code evidence is incomplete or retained → No Nuclei template listed
- 23 Oct 2026 · 09:33:49 UTC CISA KEVUnknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
- 23 Oct 2026 · 09:33:49 UTC Source coverage: public-exploit-codeIncomplete → Current
- 23 Oct 2026 · 09:33:49 UTC Source coverage: first-epssIncomplete → Current
- 23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
- 23 Oct 2026 · 09:33:49 UTC Source coverage: msrc-cvrfIncomplete → Current
- 23 Oct 2026 · 08:31:50 UTC Public exploit codeNo Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained
- 23 Oct 2026 · 08:31:50 UTC CISA KEVNot listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
- 23 Oct 2026 · 08:31:50 UTC Source coverage: public-exploit-codeCurrent → Incomplete
- 23 Oct 2026 · 08:31:50 UTC Source coverage: first-epssCurrent → Incomplete
- 23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete
Show 3 more recent changes
- 23 Oct 2026 · 08:31:50 UTCSource coverage: msrc-cvrf Current → Incomplete
- 21 Oct 2026 · 20:45:25 UTCLast revised 16 Oct 2026 01:05 UTC → 21 Oct 2026 18:42 UTC
- 18 Oct 2026 · 14:54:30 UTCLink: October 2026 → /security?release=2026-Oct#cves
The most recent 100 field changes are listed. Complete recorded revisions are kept separately.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Explore global source statements, affected packages and advisory history for CVE-2026-98419. The catalog has a separate collection scope from Microsoft release records.
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
cve-program · CVE-2026-98419
Publisheddrop_monitor: fix out-of-bounds write in reset_per_cpu_data()
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.
- Source published
- 14 Oct 2026 13:27:49 UTC
- Source modified
- 24 Oct 2026 14:08:45 UTC
- Observed here
- 24 Oct 2026 16:17:04 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H