CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down
Noroxi assessment
Priority: Monitor (action score 35/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 26c179d47403d2f919ee914cc02c31d896b59fee, 46bb297ad77680e009244f067f27d51cf5b8c7cf, 619dd29045e439d0b0f8c6d4fec1af447a050680; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 26c179d47403d2f919ee914cc02c31d896b59fee, 46bb297ad77680e009244f067f27d51cf5b8c7cf, 619dd29045e439d0b0f8c6d4fec1af447a050680; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.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: vxlan: do not arm the ageing timer on a device that is down vxlan_changelink() arms vxlan->age_timer whenever the requested ageing interval differs from the configured one: if (conf.age_interval != vxlan->cfg.age_interval) mod_timer(&vxlan->age_timer, jiffies); There is no netif_running() test, so the timer is armed even on a device that was never brought up. The only synchronous cancel in the driver is the timer_delete_sync() in vxlan_stop(), which is .ndo_stop. netif_close_many() drops devices without IFF_UP before __dev_close_many() runs, so that cancel is skipped for such a device. vxlan_setup() sets dev->needs_free_netdev = true and age_timer is a member of struct vxlan_dev, so free_netdev() releases the allocation the timer lives in while it is still queued on a timer_base. expire_timers() unlinks the entry before it loads timer->function, so the timer core writes through the freed object's list pointers: BUG: KASAN: slab-use-after-free in __run_timers+0x208/0x654 Write of size 8 at addr ffff00001adace68 by task true/192 __asan_store8+0x84/0xac __run_timers+0x208/0x654 run_timer_softirq+0x154/0x18c Allocated by task 189: alloc_netdev_mqs+0x64/0x720 rtnl_create_link+0x4ac/0x520 rtnl_newlink+0x758/0xd00 Freed by task 191: netdev_release+0x40/0x58 netdev_run_todo+0x4a4/0x8c0 rtnl_dellink+0x200/0x4e8 The rtnl operations involved are netns-scoped, so an unprivileged user can perform them in a new user and network namespace. Arming the timer on a down device never had an effect: vxlan_cleanup() returns early on !netif_running(), and vxlan_open() arms the timer for any non-zero interval once the device is brought up. Add the missing test. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>
- Published
- Aug 22, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- 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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 5.0affected
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before be44d79d14d7f9ae7c8ffb7272142005341b5123affected · git
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before 26c179d47403d2f919ee914cc02c31d896b59feeaffected · git
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before 9dc561f0522c35bdd66e0646a748814a138ec4caaffected · git
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before 619dd29045e439d0b0f8c6d4fec1af447a050680affected · git
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before 6b095e99b9e67ea31f0c4b00260e010898253519affected · git
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before 46bb297ad77680e009244f067f27d51cf5b8c7cfaffected · git
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before 6b4119af544996a545cf84b16f1dbce829ba0de8affected · git
- 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 and later · before b37971686ec59fb027fa4910ba16805e68fddb97affected · git
- before 5.0not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74613Aug 22, 2026 · vsock/virtio: avoid refilling the RX queue after teardown31Monitor
- ← EarlierCVE-2026-74614Aug 22, 2026 · vsock/virtio: read virtqueues under worker locks33Monitor
- Later →CVE-2026-74616Aug 22, 2026 · xdp: reject clones that overrun skb_shared_info tailroom39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 26c179d47403d2f919ee914cc02c31d896b59fee | Vendor (CNA) |
| Linux Linux | 46bb297ad77680e009244f067f27d51cf5b8c7cf | Vendor (CNA) |
| Linux Linux | 619dd29045e439d0b0f8c6d4fec1af447a050680 | Vendor (CNA) |
| Linux Linux | 6b095e99b9e67ea31f0c4b00260e010898253519 | Vendor (CNA) |
| Linux Linux | 6b4119af544996a545cf84b16f1dbce829ba0de8 | Vendor (CNA) |
| Linux Linux | 9dc561f0522c35bdd66e0646a748814a138ec4ca | Vendor (CNA) |
| Linux Linux | b37971686ec59fb027fa4910ba16805e68fddb97 | Vendor (CNA) |
| Linux Linux | be44d79d14d7f9ae7c8ffb7272142005341b5123 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package 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.
No dated events beyond publication.
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.
Credits
All researchersFinders, 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.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/46bb297ad77680e009244f067f27d51cf5b8c7cf
- git.kernel.org/stable/c/619dd29045e439d0b0f8c6d4fec1af447a050680
- git.kernel.org/stable/c/6b095e99b9e67ea31f0c4b00260e010898253519
- git.kernel.org/stable/c/6b4119af544996a545cf84b16f1dbce829ba0de8
- git.kernel.org/stable/c/9dc561f0522c35bdd66e0646a748814a138ec4ca
- git.kernel.org/stable/c/b37971686ec59fb027fa4910ba16805e68fddb97
- git.kernel.org/stable/c/be44d79d14d7f9ae7c8ffb7272142005341b5123
Vendor advisories and official records. Exploit/PoC links are deliberately left out.