Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-43086: ipvs: fix NULL deref in ip_vs_add_service error path

Noroxi assessment

Priority: Monitor (action score 22/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 4039959315008888dd53c37674d33351817a5166, 730663352c9178f33fcf5929f4a37c1f1ca5a693, 9a91797e61d286805ae10a92cc48959c30800556.

Low priority for now. Upgrade to Linux Linux 4039959315008888dd53c37674d33351817a5166, 730663352c9178f33fcf5929f4a37c1f1ca5a693, 9a91797e61d286805ae10a92cc48959c30800556 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 NULL deref in ip_vs_add_service error path When ip_vs_bind_scheduler() succeeds in ip_vs_add_service(), the local variable sched is set to NULL. If ip_vs_start_estimator() subsequently fails, the out_err cleanup calls ip_vs_unbind_scheduler(svc, sched) with sched == NULL. ip_vs_unbind_scheduler() passes the cur_sched NULL check (because svc->scheduler was set by the successful bind) but then dereferences the NULL sched parameter at sched->done_service, causing a kernel panic at offset 0x30 from NULL. Oops: general protection fault, [..] [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] RIP: 0010:ip_vs_unbind_scheduler (net/netfilter/ipvs/ip_vs_sched.c:69) Call Trace: <TASK> ip_vs_add_service.isra.0 (net/netfilter/ipvs/ip_vs_ctl.c:1500) do_ip_vs_set_ctl (net/netfilter/ipvs/ip_vs_ctl.c:2809) nf_setsockopt (net/netfilter/nf_sockopt.c:102) [..] Fix by simply not clearing the local sched variable after a successful bind. ip_vs_unbind_scheduler() already detects whether a scheduler is installed via svc->scheduler, and keeping sched non-NULL ensures the error path passes the correct pointer to both ip_vs_unbind_scheduler() and ip_vs_scheduler_put(). While the bug is older, the problem popups in more recent kernels (6.2), when the new error path is taken after the ip_vs_start_estimator() call.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 6, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-2026-43086

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.2.1 and later · before 6.6.136
  • linux linux kernel6.7 and later · before 6.12.83
  • linux linux kernel6.13 and later · before 6.18.24
  • linux linux kernel6.19 and later · before 6.19.14
  • linux linux kernel6.2
  • linux linux kernel7.0

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

    • 6.2affected
    • 705dd34440812735ece298eb5bc153fde9544d42 and later · before 730663352c9178f33fcf5929f4a37c1f1ca5a693affected · git
    • 705dd34440812735ece298eb5bc153fde9544d42 and later · before 4039959315008888dd53c37674d33351817a5166affected · git
    • 705dd34440812735ece298eb5bc153fde9544d42 and later · before a32dabacee111cea083ddd57a03635672e1bff29affected · git
    • 705dd34440812735ece298eb5bc153fde9544d42 and later · before c2ddbe577e2ebf63f2d8fb15cdc7503af70f3e94affected · git
    • 705dd34440812735ece298eb5bc153fde9544d42 and later · before 9a91797e61d286805ae10a92cc48959c30800556affected · git
    • before 6.2not affected · semver
    • 6.6.136 and later · up to and including 6.6.*not affected · semver
    • 6.12.83 and later · up to and including 6.12.*not affected · semver
    • 6.18.24 and later · up to and including 6.18.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.14-16.19.14-1
SUSE:Linux Micro 6.0kernel-defaultbefore 6.4.0-49.16.4.0-49.1
SUSE:Linux Micro 6.0kernel-kvmsmallbefore 6.4.0-49.16.4.0-49.1
SUSE:Linux Micro 6.0kernel-rtbefore 6.4.0-49.16.4.0-49.1
SUSE:Linux Micro 6.0kernel-sourcebefore 6.4.0-49.16.4.0-49.1
SUSE:Linux Micro 6.0kernel-source-rtbefore 6.4.0-49.16.4.0-49.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43081May 6, 2026 · net: ipa: fix GENERIC_CMD register field masks for IPA v5.0+
    22Monitor
  • ← EarlierCVE-2026-43082May 6, 2026 · net: txgbe: leave space for null terminators on property_entry
    22Monitor
  • Later →CVE-2026-43087May 6, 2026 · pinctrl: mcp23s08: Disable all pin interrupts during probe
    22Monitor

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 Linux4039959315008888dd53c37674d33351817a5166Vendor (CNA)
Linux Linux730663352c9178f33fcf5929f4a37c1f1ca5a693Vendor (CNA)
Linux Linux9a91797e61d286805ae10a92cc48959c30800556Vendor (CNA)
Linux Linuxa32dabacee111cea083ddd57a03635672e1bff29Vendor (CNA)
Linux Linuxc2ddbe577e2ebf63f2d8fb15cdc7503af70f3e94Vendor (CNA)
debian:linux6.12.85-1 · Debian:13Package registry (OSV)
suse:kernel-default6.4.0-49.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-kvmsmall6.4.0-49.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-rt6.4.0-49.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-source6.4.0-49.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-source-rt6.4.0-49.1 · SUSE:Linux Micro 6.0Package 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.

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

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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