Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path

Noroxi assessment

Priority: Monitor (action score 0/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.20% (FIRST EPSS).
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 25ab24df31f7af843c96a38e0781b9165216e1a8, 3.19, 312d7cd88882fc6cadcc08b02287497aaaf94bcd.

Low priority for now. Upgrade to Linux Linux 25ab24df31f7af843c96a38e0781b9165216e1a8, 3.19, 312d7cd88882fc6cadcc08b02287497aaaf94bcd 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: ipvs: fix ipv4 null-ptr-deref in route error path The IPv4 code path in __ip_vs_get_out_rt() calls dst_link_failure() without ensuring skb->dev is set, leading to a NULL pointer dereference in fib_compute_spec_dst() when ipv4_link_failure() attempts to send ICMP destination unreachable messages. The issue emerged after commit ed0de45a1008 ("ipv4: recompile ip options in ipv4_link_failure") started calling __ip_options_compile() from ipv4_link_failure(). This code path eventually calls fib_compute_spec_dst() which dereferences skb->dev. An attempt was made to fix the NULL skb->dev dereference in commit 0113d9c9d1cc ("ipv4: fix null-deref in ipv4_link_failure"), but it only addressed the immediate dev_net(skb->dev) dereference by using a fallback device. The fix was incomplete because fib_compute_spec_dst() later in the call chain still accesses skb->dev directly, which remains NULL when IPVS calls dst_link_failure(). The crash occurs when: 1. IPVS processes a packet in NAT mode with a misconfigured destination 2. Route lookup fails in __ip_vs_get_out_rt() before establishing a route 3. The error path calls dst_link_failure(skb) with skb->dev == NULL 4. ipv4_link_failure() → ipv4_send_dest_unreach() → __ip_options_compile() → fib_compute_spec_dst() 5. fib_compute_spec_dst() dereferences NULL skb->dev Apply the same fix used for IPv6 in commit 326bf17ea5d4 ("ipvs: fix ipv6 route unreach panic"): set skb->dev from skb_dst(skb)->dev before calling dst_link_failure(). KASAN: null-ptr-deref in range [0x0000000000000328-0x000000000000032f] CPU: 1 PID: 12732 Comm: syz.1.3469 Not tainted 6.6.114 #2 RIP: 0010:__in_dev_get_rcu include/linux/inetdevice.h:233 RIP: 0010:fib_compute_spec_dst+0x17a/0x9f0 net/ipv4/fib_frontend.c:285 Call Trace: <TASK> spec_dst_fill net/ipv4/ip_options.c:232 spec_dst_fill net/ipv4/ip_options.c:229 __ip_options_compile+0x13a1/0x17d0 net/ipv4/ip_options.c:330 ipv4_send_dest_unreach net/ipv4/route.c:1252 ipv4_link_failure+0x702/0xb80 net/ipv4/route.c:1265 dst_link_failure include/net/dst.h:437 __ip_vs_get_out_rt+0x15fd/0x19e0 net/netfilter/ipvs/ip_vs_xmit.c:412 ip_vs_nat_xmit+0x1d8/0xc80 net/netfilter/ipvs/ip_vs_xmit.c:764

—No exploit Fix available
Published
Jan 13, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2025-68813

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 6c2fa855d8178699706b1192db2f1f8102b0ba1e, fbf569d2beee2a4a7a0bc8b619c26101d1211a88, ff71f99d5fb2daf54340e8b290d0bc4e6b4c1d38, 3d988fcddbe7b8673a231958bd2fba61b5a7ced9, 8a430e56a6485267a1b2d3747209d26c54d1a34b, 6bd1ee0a993fc9574ae43c1994c54a60cb23a380, 5.1affected
    • ed0de45a1008991fdaa27a0152befcb74d126a8b and later · before dd72a93c80408f06327dd2d956eb1a656d0b5903affected · git
    • ed0de45a1008991fdaa27a0152befcb74d126a8b and later · before 312d7cd88882fc6cadcc08b02287497aaaf94bcdaffected · git
    • ed0de45a1008991fdaa27a0152befcb74d126a8b and later · before cdeff10851c37a002d87a035818ebd60fdb74447affected · git
    • ed0de45a1008991fdaa27a0152befcb74d126a8b and later · before 4729ff0581fbb7ad098b6153b76b6f5aac94618aaffected · git
    • ed0de45a1008991fdaa27a0152befcb74d126a8b and later · before 25ab24df31f7af843c96a38e0781b9165216e1a8affected · git
    • ed0de45a1008991fdaa27a0152befcb74d126a8b and later · before 689a627d14788ad772e0fa24c2e57a23dbc7ce90affected · git
    • ed0de45a1008991fdaa27a0152befcb74d126a8b and later · before ad891bb3d079a46a821bf2b8867854645191bab0affected · git
    • 3.18.139 and later · before 3.19affected · semver
    • 4.4.179 and later · before 4.5affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_65before 15-2.115-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_67before 14-2.114-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_68before 12-2.112-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_70before 11-2.111-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_72before 7-2.17-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_73before 5-2.15-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_75before 3-2.13-2.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_76before 3-2.13-2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_36before 16-150400.2.216-150400.2.2
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_37before 16-150400.2.216-150400.2.2
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_44before 9-150400.2.19-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_45before 7-150400.2.17-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_47before 3-150400.2.13-150400.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_24before 16-150500.2.216-150500.2.2
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_25before 15-150500.2.215-150500.2.2
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_27before 14-150500.2.114-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_29before 11-150500.2.111-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_31before 6-150500.2.16-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_34before 3-150500.2.13-150500.2.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_10before 14-150600.2.214-150600.2.2
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_12before 13-150600.2.113-150600.2.1

+49

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68809Jan 13, 2026 · ksmbd: vfs: fix race on m_flags in vfs_cache
    36Monitor
  • ← EarlierCVE-2025-68811Jan 13, 2026 · svcrdma: use rc_pageoff for memcpy byte offset
    39Monitor
  • Later →CVE-2025-68814Jan 13, 2026 · io_uring: fix filename leak in __io_openat_prep()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux25ab24df31f7af843c96a38e0781b9165216e1a8Vendor (CNA)
Linux Linux3.19Vendor (CNA)
Linux Linux312d7cd88882fc6cadcc08b02287497aaaf94bcdVendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux4729ff0581fbb7ad098b6153b76b6f5aac94618aVendor (CNA)
Linux Linux5.1Vendor (CNA)
Linux Linux689a627d14788ad772e0fa24c2e57a23dbc7ce90Vendor (CNA)
Linux Linuxad891bb3d079a46a821bf2b8867854645191bab0Vendor (CNA)
Linux Linuxcdeff10851c37a002d87a035818ebd60fdb74447Vendor (CNA)
Linux Linuxdd72a93c80408f06327dd2d956eb1a656d0b5903Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_012-150700.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_112-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_211-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_63-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_72-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_82-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_6515-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_6812-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_727-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_735-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_753-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_763-2.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package 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.

No history yet (it accumulates with the daily EPSS job).

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.

Finders, 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.

  • CVE-2026-68136209 days apartnet: gro: fix double aggregation of flush-marked skbs
    39Monitor
  • CVE-2026-68385209 days aparts390/checksum: Fix csum_partial() without vector facility
    39Monitor
  • CVE-2025-688180 days apartscsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path"
    35Monitor
  • CVE-2026-68354209 days apartfirewire: net: Fix fragmented datagram reassembly
    35Monitor
  • CVE-2026-72035214 days apartnet/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked
    32Monitor
  • CVE-2026-68305209 days apartdrm/xe/vf: Add drm_dev guards when detaching CCS read/write buffers
    31Monitor

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).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records