CVE-2026-68287: Linux kernel · drop_monitor: fix size calculations for 64-bit attributes
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 925669d4cfd47a9019ab29b40676215bab5dae35 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:30 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in 925669d4cfd47a9019ab29b40676215bab5dae35, 7089f7ab99c89f443c92d8fcc585e63f2727f0b3, 6048ed2dfb33426c8aef32f8d225ea91c66813db +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: drop_monitor: fix size calculations for 64-bit attributes net_dm_packet_report_fill() and net_dm_hw_packet_report_fill() use nla_put_u64_64bit() to append 64-bit attributes (NET_DM_ATTR_PC and NET_DM_ATTR_TIMESTAMP). On 32-bit architectures without CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS, nla_put_u64_64bit() may append a 4-byte NET_DM_ATTR_PAD attribute for 64-bit alignment. However, net_dm_packet_report_size() and net_dm_hw_packet_report_size() used nla_total_size(sizeof(u64)) instead of nla_total_size_64bit(sizeof(u64)), budgeting 12 bytes instead of up to 16 bytes. This under-estimation of SKB size can lead to an skb_over_panic() when __nla_reserve() or skb_put() is subsequently called. Fix this by using nla_total_size_64bit(sizeof(u64)) in both size calculations.
References
- git.kernel.org/stable/c/1275a4769c126405c6c63b6372daff120ac679a6 (opens in a new tab)
- git.kernel.org/stable/c/0da8f531336b28a59b23e5a67d40eaed15906201 (opens in a new tab)
- git.kernel.org/stable/c/6048ed2dfb33426c8aef32f8d225ea91c66813db (opens in a new tab)
- git.kernel.org/stable/c/925669d4cfd47a9019ab29b40676215bab5dae35 (opens in a new tab)
- git.kernel.org/stable/c/4a9e30764e80693bcf875c776170edce20f94fe0 (opens in a new tab)
- git.kernel.org/stable/c/7089f7ab99c89f443c92d8fcc585e63f2727f0b3 (opens in a new tab)