BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-43086High confidence

ipvs: fix NULL deref in ip_vs_add_service error path

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.14-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-43086 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-43086
105 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
Summary
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: 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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-27582

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1385Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=CVE-2026-43081 Référence CVE CVE-2026-43082 https://www.cve.org/CVERecord?id=CVE-2026-43082 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43084 https://www.cve.org/CVERecord?id=CVE-2026-43084 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43091 https://www.cve.org/CVERecord?id=CVE-2026-43091 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43099 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0956Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43057 https://www.cve.org/CVERecord?id=CVE-2026-43057 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=CVE-2026-43081 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43090 https://www.cve.org/CVERecord?id=CVE-2026-43090 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43107 https://www.cve.org/CVERecord?id=CVE-2026-43107 Référence CVE CVE-2026-43119 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=CVE-2026-43081 Référence CVE CVE-2026-43082 https://www.cve.org/CVERecord?id=CVE-2026-43082 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43084 https://www.cve.org/CVERecord?id=CVE-2026-43084 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43091 https://www.cve.org/CVERecord?id=CVE-2026-43091 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43099 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43062 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=CVE-2026-43081 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43090 https://www.cve.org/CVERecord?id=CVE-2026-43090 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43104 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=CVE-2026-43081 Référence CVE CVE-2026-43082 https://www.cve.org/CVERecord?id=CVE-2026-43082 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43084 https://www.cve.org/CVERecord?id=CVE-2026-43084 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43091 https://www.cve.org/CVERecord?id=CVE-2026-43091 Référence CVE CVE-2026-43092 https://www.cve.org/CVERecord?id=CVE-2026-43092 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43098 https://www.cve.org/CVERecord?id=CVE-2026-43098 Référence CVE CVE-2026-43099 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0864Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=CVE-2026-43081 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43107 https://www.cve.org/CVERecord?id=CVE-2026-43107 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43119 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-017830LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。ipvsのip_vs_add_service()関数のエラーパスにおけるNULL参照の問題です。ip_vs_add_service()内でip_vs_bind_scheduler()が成功すると、ローカル変数schedはNULLに設定されます。その後、ip_vs_start_estimator()が失敗すると、out_errのクリーンアップ処理でip_vs_unbind_scheduler(svc, sched)がsched==NULLの状態で呼び出されます。ip_vs_unbind_scheduler()はcur_schedのNULLチェックを通過します（svc-schedulerはbind成功時に設定されているため）が、その後schedパラメータのNULL参照（sched-done_service）が発生し、NULLからオフセット0x30でカーネルパニックが発生します。エラーメッセージは以下の通りです。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: 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) などです。対策としては、成功したbind後にローカル変数schedをクリアしないようにします。ip_vs_unbind_scheduler()はsvc-schedulerを通じてスケジューラの有無をすでに検出しており、schedをNULL以外に保持することで、エラーパスにおいてip_vs_unbind_scheduler()およびip_vs_scheduler_put()に正しいポインタを渡せるようにします。このバグ自体は古いものですが、問題はip_vs_start_estimator()呼び出し後の新しいエラーパスが取られる最近のカーネル（6.2）で顕在化しています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.2, 6.6.136 ≤ 6.6.*, 6.12.83 ≤ 6.12.*, 6.18.24 ≤ 6.18.*, 6.19.14 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 6 May 2026 · Last source change 11 May 2026, 22:17 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-27582
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-27582↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-43086 · cve.blacktree.nl