Full vulnerability report · 2026

CVE-2026-53184High confidence

udp: clear skb->dev before running a sockmap verdict

Linux · Linux

7.5HighCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. 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

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

No CISA KEV confirmation is currently recorded.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.48% for the current model date.

Compensating controls

Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Monitor vendor guidance and exploitation sources for a material change.

Verification

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

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.

Canonical Ubuntu Security: 20 affected package states with no published fix

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 release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.12.94-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.1.176-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.0.13-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`7.0.13-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical 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-53184 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-53184

76 known affected

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

kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7

Summary: In the Linux kernel, the following vulnerability has been resolved: udp: clear skb->dev before running a sockmap verdict On the UDP receive path skb->dev is repurposed as dev_scratch (the truesize/state cache set by udp_set_dev_scratch()), through the union { struct net_device *dev; unsigned long dev_scratch; } in sk_buff. When a UDP socket is in a sockmap, sk_data_ready is sk_psock_verdict_data_ready(), which calls udp_read_skb() -> recv_actor() (sk_psock_verdict_recv) to run the attached SK_SKB verdict program in softirq. If that program calls a socket-lookup helper (bpf_sk_lookup_tcp/udp, bpf_skc_lookup_tcp), bpf_skc_lookup() does: if (skb->dev) caller_net = dev_net(skb->dev); skb->dev still holds the dev_scratch value (a non-NULL integer), so dev_net() dereferences it as a struct net_device * and the kernel takes a general protection fault on a non-canonical address in softirq: Oops: general protection fault, probably for non-canonical address 0x1010000800004a0 CPU: 1 UID: 0 PID: 1406 Comm: syz.2.19 Not tainted 7.1.0-rc6 #1 PREEMPT(full) RIP: 0010:bpf_skc_lookup net/core/filter.c:7033 [inline] RIP: 0010:bpf_sk_lookup+0x45/0x160 net/core/filter.c:7047 Call Trace: bpf_prog_4675cb904b7071f8+0x12e/0x14e bpf_prog_run_pin_on_cpu+0xc6/0x1f0 sk_psock_verdict_recv+0x1ba/0x350 udp_read_skb+0x31a/0x370 sk_psock_verdict_data_ready+0x2e3/0x600 __udp_enqueue_schedule_skb+0x4c8/0x650 udpv6_queue_rcv_one_skb+0x3ec/0x740 udp6_unicast_rcv_skb+0x11d/0x140 ip6_protocol_deliver_rcu+0x61e/0x950 ip6_input_finish+0xa9/0x150 NF_HOOK+0x286/0x2f0 ip6_input+0x117/0x220 NF_HOOK+0x286/0x2f0 __netif_receive_skb+0x85/0x200 process_backlog+0x374/0x9a0 __napi_poll+0x4f/0x1c0 net_rx_action+0x3b0/0x770 handle_softirqs+0x15a/0x460 do_softirq+0x57/0x80 The rmem charge that dev_scratch accounted for is released by skb_recv_udp() on dequeue, just above, so the scratch is dead by the time recv_actor() runs. Clear skb->dev so bpf_skc_lookup() falls back to sock_net(skb->sk), which skb_set_owner_sk_safe() set just above.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

In the Linux kernel, the following vulnerability has been resolved: udp: clear skb->dev before running a sockmap verdict On the UDP receive path skb->dev is repurposed as dev_scratch (the truesize/state cache set by udp_set_dev_scratch()), through the union { struct net_device *dev; unsigned long dev_scratch; } in sk_buff. When a UDP socket is in a sockmap, sk_data_ready is sk_psock_verdict_data_ready(), which calls udp_read_skb() -> recv_actor() (sk_psock_verdict_recv) to run the attached SK_SKB verdict program in softirq. If that program calls a socket-lookup helper (bpf_sk_lookup_tcp/udp, bpf_skc_lookup_tcp), bpf_skc_lookup() does: if (skb->dev) caller_net = dev_net(skb->dev); skb->dev still holds the dev_scratch value (a non-NULL integer), so dev_net() dereferences it as a struct net_device * and the kernel takes a general protection fault on a non-canonical address in softirq: Oops: general protection fault, probably for non-canonical address 0x1010000800004a0 CPU: 1 UID: 0 PID: 1406 Comm: syz.2.19 Not tainted 7.1.0-rc6 #1 PREEMPT(full) RIP: 0010:bpf_skc_lookup net/core/filter.c:7033 [inline] RIP: 0010:bpf_sk_lookup+0x45/0x160 net/core/filter.c:7047 Call Trace: <IRQ> bpf_prog_4675cb904b7071f8+0x12e/0x14e bpf_prog_run_pin_on_cpu+0xc6/0x1f0 sk_psock_verdict_recv+0x1ba/0x350 udp_read_skb+0x31a/0x370 sk_psock_verdict_data_ready+0x2e3/0x600 __udp_enqueue_schedule_skb+0x4c8/0x650 udpv6_queue_rcv_one_skb+0x3ec/0x740 udp6_unicast_rcv_skb+0x11d/0x140 ip6_protocol_deliver_rcu+0x61e/0x950 ip6_input_finish+0xa9/0x150 NF_HOOK+0x286/0x2f0 ip6_input+0x117/0x220 NF_HOOK+0x286/0x2f0 __netif_receive_skb+0x85/0x200 process_backlog+0x374/0x9a0 __napi_poll+0x4f/0x1c0 net_rx_action+0x3b0/0x770 handle_softirqs+0x15a/0x460 do_softirq+0x57/0x80 </IRQ> The rmem charge that dev_scratch accounted for is released by skb_recv_udp() on dequeue, just above, so the scratch is dead by the time recv_actor() runs. Clear skb->dev so bpf_skc_lookup() falls back to sock_net(skb->sk), which skb_set_owner_sk_safe() set just above.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

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: a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
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.: CWE not yet assigned
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:L/PR:N/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.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticated

Official authority intelligence

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

ENISA EUVD · EUVD-2026-39275Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

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

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

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

d?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53178 https://www.cve.org/CVERecord?id=CVE-2026-53178 Référence CVE CVE-2026-53179 https://www.cve.org/CVERecord?id=CVE-2026-53179 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 https://www.cve.org/CVERecord?id=CVE-2026-53183 Référence CVE CVE-2026-53184 https://www.cve.org/CVERecord?id=CVE-2026-53184 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53187 https://www.cve.org/CVERecord?id=CVE-2026-53187 Référence CVE CVE-2026-53188 https://www.cve.org/CVERecord?id=CVE-2026-53188 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53190 https://www.cve.org/CVERecord?id=CVE-2026-53190 Référence CVE CVE-2026-53191 https://www.cve.org/CVERecord?id=CVE-2026-53191 Référence CVE CVE-2026-53192 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

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

d?id=CVE-2026-53173 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53178 https://www.cve.org/CVERecord?id=CVE-2026-53178 Référence CVE CVE-2026-53179 https://www.cve.org/CVERecord?id=CVE-2026-53179 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 https://www.cve.org/CVERecord?id=CVE-2026-53183 Référence CVE CVE-2026-53184 https://www.cve.org/CVERecord?id=CVE-2026-53184 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53187 https://www.cve.org/CVERecord?id=CVE-2026-53187 Référence CVE CVE-2026-53188 https://www.cve.org/CVERecord?id=CVE-2026-53188 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53190 https://www.cve.org/CVERecord?id=CVE-2026-53190 Référence CVE CVE-2026-53191 https://www.cve.org/CVERecord?id=CVE-2026-53191 Référence CVE CVE-2026-53192 https://www.cve.org/CVERecord?id=

Official advisory ↗

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

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53129 Référence CVE CVE-2026-53131 https://www.cve.org/CVERecord?id=CVE-2026-53131 Référence CVE CVE-2026-53132 https://www.cve.org/CVERecord?id=CVE-2026-53132 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53134 https://www.cve.org/CVERecord?id=CVE-2026-53134 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 https://www.cve.org/CVERecord?id=CVE-2026-53183 Référence CVE CVE-2026-53184 https://www.cve.org/CVERecord?id=CVE-2026-53184 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53158 Référence CVE CVE-2026-53159 https://www.cve.org/CVERecord?id=CVE-2026-53159 Référence CVE CVE-2026-53160 https://www.cve.org/CVERecord?id=CVE-2026-53160 Référence CVE CVE-2026-53161 https://www.cve.org/CVERecord?id=CVE-2026-53161 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 https://www.cve.org/CVERecord?id=CVE-2026-53183 Référence CVE CVE-2026-53184 https://www.cve.org/CVERecord?id=CVE-2026-53184 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53190 https://www.cve.org/CVERecord?id=CVE-2026-53190 Référence CVE CVE-2026-53191 https://www.cve.org/CVERecord?id=CVE-2026-53191 Référence CVE CVE-2026-53192 https://www.cve.org/CVERecord?id=CVE-2026-53192 Référence CVE CVE-2026-53193 https://www.cve.org/CVERecord?id=CVE-2026-53193 Référence CVE CVE-2026-53195 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-53163 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 Référence CVE CVE-2026-53168 https://www.cve.org/CVERecord?id=CVE-2026-53168 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53179 https://www.cve.org/CVERecord?id=CVE-2026-53179 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 https://www.cve.org/CVERecord?id=CVE-2026-53183 Référence CVE CVE-2026-53184 https://www.cve.org/CVERecord?id=CVE-2026-53184 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53194 https://www.cve.org/CVERecord?id=CVE-2026-53194 Référence CVE CVE-2026-53195 https://www.cve.org/CVERecord?id=CVE-2026-53195 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53198 https://www.cve.org/CVERecord?id=CVE-2026-53198 Référence CVE CVE-2026-53199 https://www.cve.org/CVERecord?id=CVE-2026-53199 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0812Multiples vulnérabilités dans Microsoft Azure Linux

ulletin de sécurité Microsoft CVE-2026-53154 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53158 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53159 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53160 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53161 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53176 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53177 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53181 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53182 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53183 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53184 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53186 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53194 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53196 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53199 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53207 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53209 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53213 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53214 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53215 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53217 du 27 juin 2026 Bulletin de s

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-022492LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました:udp: sockmap の verdict を実行する前に skb->dev をクリアするUDP の受信パスでは、sk_buff 内の union { struct net_device *dev; unsigned long dev_scratch; } を介して、skb->dev は dev_scratch（udp_set_dev_scratch() によって設定される truesize/状態キャッシュ）として再利用されます。UDP ソケットが sockmap にある場合、sk_data_ready は sk_psock_verdict_data_ready() となり、softirq で添付された SK_SKB verdict プログラムを実行するために udp_read_skb() -> recv_actor()（sk_psock_verdict_recv）を呼び出します。そのプログラムがソケット検索ヘルパー（bpf_sk_lookup_tcp/udp、bpf_skc_lookup_tcp）を呼ぶと、bpf_skc_lookup() は次を実行します:\tif (skb->dev)\t\tcaller_net = dev_net(skb->dev);skb->dev には依然として dev_scratch の値（NULL ではない整数）が保持されているため、dev_net() はそれを struct net_device * として参照外しし、softirq 中に非正規アドレスで General Protection Fault が発生します: Oops: general protection fault, probably for non-canonical address 0x1010000800004a0 CPU: 1 UID: 0 PID: 1406 Comm: syz.2.19 Not tainted 7.1.0-rc6 #1 PREEMPT(full) RIP: 0010:bpf_skc_lookup net/core/filter.c:7033 [inline] RIP: 0010:bpf_sk_lookup+0x45/0x160 net/core/filter.c:7047 Call Trace: bpf_prog_4675cb904b7071f8+0x12e/0x14e bpf_prog_run_pin_on_cpu+0xc6/0x1f0 sk_psock_verdict_recv+0x1ba/0x350 udp_read_skb+0x31a/0x370 sk_psock_verdict_data_ready+0x2e3/0x600 __udp_enqueue_schedule_skb+0x4c8/0x650 udpv6_queue_rcv_one_skb+0x3ec/0x740 udp6_unicast_rcv_skb+0x11d/0x140 ip6_protocol_deliver_rcu+0x61e/0x950 ip6_input_finish+0xa9/0x150 NF_HOOK+0x286/0x2f0 ip6_input+0x117/0x220 NF_HOOK+0x286/0x2f0 __netif_receive_skb+0x85/0x200 process_backlog+0x374/0x9a0 __napi_poll+0x4f/0x1c0 net_rx_action+0x3b0/0x770 handle_softirqs+0x15a/0x460 do_softirq+0x57/0x80 dev_scratch が計上していた rmem チャージは、その直前のデキュー時に skb_recv_udp() によって解放されるため、recv_actor() が実行される時点では scratch はすでに無効です。したがって skb->dev をクリアし、bpf_skc_lookup() が sock_net(skb->sk) にフォールバックするようにします。これは直前で skb_set_owner_sk_safe() によって設定されています。

Official advisory ↗

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: kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP7
kernel-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7
kernel-source as component of SUSE Linux Enterprise Module for Legacy 15 SP7
reiserfs-kmp-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7
kernel-default as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7
kernel-source as component of SUSE Linux Enterprise Module for Public Cloud 15 SP7
cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
and 46 more
Fixed: Linux: < 6.0, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 25 Jun 2026 · Last source change 5 Aug 2026, 12:33 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2

CVSS sourceCNA

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-39275

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceUnavailable

NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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.

2026-06-25CVE published

2026-08-05Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-39275↗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.

udp: clear skb->dev before running a sockmap verdict

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

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

ENISA European Vulnerability Database

EUVD-2026-39275

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication