CVE-2025-68353
NoneCVSS
—
EPSS
0.2%
Published
Dec 24, 2025
CISA due date
—
Cloudanix analysis
A bug in the Linux kernel's network handling can cause the entire system to crash when certain network interfaces are disabled, potentially disrupting services until the machine is restarted.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Low
- Impact
- Denial Of Service
- Component
- OS kernel
- Class
- Memory Corruption
- Remediation
- Patch
- Effort
- Medium
- Patch risk
- Low
What it actually does
NULL pointer dereference in vxlan_xmit_one when sock4 or sock6 are invalid (e.g., interface down), causing kernel oops during VXLAN transmit path.
Why it matters to the business
Unexpected kernel crashes on systems using VXLAN networking can lead to service outages, loss of network connectivity, and require manual reboots or restarts, increasing operational overhead especially on high-availability or containerized environments.
How an attack unfolds
An attacker with the ability to influence network interface state or VXLAN configuration triggers the transmit path under conditions where socket pointers are NULL, resulting in a kernel panic; no authenticated remote code execution is indicated.
How to fix it
Update the Linux kernel to a version containing commit 4ac26aafdc8c7271414e2e7c0b2cb266a26591bc or later; rebuild and deploy affected images such as prometheus-pushgateway-fips to version 1.11.0-r4 or newer.
How to confirm the fix worked
Verify the running kernel contains the fix commit or is newer than the vulnerable release; reproduce interface-down scenarios while monitoring for absence of the described NULL dereference oops in dmesg or kernel logs.
Typical attack path
- Identify or configure a system using VXLAN interfaces
- Bring the relevant network interface down or manipulate routing state
- Trigger packet transmission through the VXLAN device
- Cause vxlan_xmit_one to dereference a NULL sock pointer
- Induce kernel NULL pointer dereference and system crash
How to detect it
Search kernel logs and dmesg for NULL pointer dereference oops with stack traces containing vxlan_xmit_one, vxlan_xmit, and related IP output functions; correlate with recent interface state changes.
- BUG: kernel NULL pointer dereference, address: 0000000000000010
- vxlan_xmit_one+0xbb3/0x1580
- vxlan_xmit+0x429/0x610
- Oops: Oops: 0000 [#1] SMP NOPTI
What your security team should do
- Prioritize kernel updates on all systems using VXLAN
- Monitor for kernel oops involving vxlan_xmit_one
- Test interface state changes in staging environments before production rollout
- Review downstream package dependencies for the fixed commit
The record
In the Linux kernel, the following vulnerability has been resolved: net: vxlan: prevent NULL deref in vxlan_xmit_one Neither sock4 nor sock6 pointers are guaranteed to be non-NULL in vxlan_xmit_one, e.g. if the iface is brought down. This can lead to the following NULL dereference: BUG: kernel NULL pointer dereference, address: 0000000000000010 Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:vxlan_xmit_one+0xbb3/0x1580 Call Trace: vxlan_xmit+0x429/0x610 dev_hard_start_xmit+0x55/0xa0 __dev_queue_xmit+0x6d0/0x7f0 ip_finish_output2+0x24b/0x590 ip_output+0x63/0x110 Mentioned commits changed the code path in vxlan_xmit_one and as a side effect the sock4/6 pointer validity checks in vxlan(6)_get_route were lost. Fix this by adding back checks. Since both commits being fixed were released in the same version (v6.7) and are strongly related, bundle the fixes in a single commit.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Linux | Kernel | 6.7.0 | 6.18.2 |
| openSUSE:Leap 16.0 | dtb-aarch64 | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-64kb | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-azure | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default-base | 0 | 6.12.0-160000.9.1.160000.2.6 |
| openSUSE:Leap 16.0 | kernel-docs | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-rt | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-source | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-syms | 0 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | 0 | 6.12.0-160000.9.1 |
| openSUSE:Tumbleweed | kernel-source | 0 | 6.18.5-1.1 |
| openSUSE:Tumbleweed | kernel-source-longterm | 0 | 6.18.16-1.1 |
Related vulnerabilities
- CVE-2026-23226 In the Linux kernel, the following vulnerability has been resolved: ksmbd: add chann_lock… Also affects Kernel
- CVE-2026-23225 In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't… Also affects Kernel
- CVE-2026-23230 In the Linux kernel, the following vulnerability has been resolved: smb: client: split… Also affects Kernel
- CVE-2026-23224 In the Linux kernel, the following vulnerability has been resolved: erofs: fix UAF issue… Also affects Kernel
- CVE-2026-23227 In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use… Also affects Kernel
- CVE-2026-23223 In the Linux kernel, the following vulnerability has been resolved: xfs: fix UAF in… Also affects Kernel
- CVE-2026-23228 In the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak… Also affects Kernel
- CVE-2026-23229 In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add… Also affects Kernel