Skip to main content

Linux Kernel CVE-2026-52920

| EUVDEUVD-2026-38723 HIGH
2026-06-24 Linux GHSA-qgcc-gwgq-pq62
8.3
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.3 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
vuln.today AI
5.6 MEDIUM

Triggered by inbound packets (PR:N) but only against a non-default strict multi-element xt_policy IPsec ruleset (AC:H); impact is a limited policy-matching bypass affecting filtering integrity, with minor confidentiality and availability effects.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
SUSE
4.8 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 28, 2026 - 08:23 vuln.today
CVSS changed
Jun 28, 2026 - 08:22 NVD
8.3 (HIGH)
Patch available
Jun 24, 2026 - 09:16 EUVD
CVE Published
Jun 24, 2026 - 07:14 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 24, 2026 - 07:14 cve.org
HIGH 8.3

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

netfilter: xt_policy: fix strict mode inbound policy matching

match_policy_in() walks sec_path entries from the last transform to the first one, but strict policy matching needs to consume info->pol[] in the same forward order as the rule layout.

Derive the strict-match policy position from the number of transforms already consumed so that multi-element inbound rules are matched consistently.

AnalysisAI

Incorrect strict-mode policy matching in the Linux kernel's netfilter xt_policy module causes multi-element inbound IPsec policy rules to be evaluated in the wrong order, so packets can be matched against the wrong transform descriptor. On systems that filter inbound traffic with iptables/nftables 'policy' matches in strict mode using multiple policy elements, this can let traffic that should be rejected satisfy the rule (or legitimate IPsec traffic fail it), undermining the intended firewall/IPsec enforcement. There is no public exploit identified at time of analysis and EPSS is low (0.16%, 6th percentile); the issue has been resolved upstream with stable patches available.

Technical ContextAI

The flaw lives in netfilter's xt_policy match extension (the iptables/nftables '-m policy' module), which inspects the IPsec secpath (sec_path) attached to a packet to verify it traversed expected IPsec transforms (ESP/AH, tunnel/transport, with given SPI/reqid/addresses). In strict mode a rule lists an ordered array of policy elements (info->pol[]) that must correspond one-to-one with the chain of applied transforms. The bug is an ordering/indexing error: match_policy_in() iterates the inbound secpath entries from the last transform back to the first, but strict matching needs to consume info->pol[] in the same forward order as the rule was written. The fix derives the strict-match policy index from the number of transforms already consumed, restoring consistent matching for multi-element inbound rules. No CWE was assigned, but this is a logic/ordering error class (improper validation of the security-policy chain) rather than a memory-safety defect.

RemediationAI

Apply the vendor-released patch by upgrading to a fixed stable kernel: 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, or 7.1 (or later within each series), matching your distribution's backport. The corresponding upstream commits are published at git.kernel.org (e.g. https://git.kernel.org/stable/c/eb323f7b82d2e2f638de0cc2a177803eb20e0707 and the sibling stable commits), and the issue is catalogued at https://nvd.nist.gov/vuln/detail/CVE-2026-52920. If immediate patching is not possible, audit your firewall rules and avoid relying on xt_policy strict mode with multiple policy elements for inbound matching; rewrite affected rules as single-element matches or enforce the equivalent constraint with separate sequential rules/XFRM policy, accepting that this is more verbose and harder to maintain. As defense in depth, do not treat the xt_policy match as the sole IPsec-enforcement boundary while unpatched, and validate that inbound IPsec-protected flows are still accepted to avoid accidentally dropping legitimate traffic.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-52920 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy