Linux Kernel up to 7.1-rc2 xfrm auth_data privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc2. It has been classified as problematic. Affected is the function auth_data of the component xfrm. Performing a manipulation results in an unknown weakness. This vulnerability is identified as CVE-2026-46193. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc2. This affects the function auth_data of the component xfrm. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: xfrm: ah: account for ESN high bits in async callbacks AH allocates its temporary auth/ICV layout differently when ESN is enabled: the async ahash setup appends a 4-byte seqhi slot before the ICV or auth_data area, but the async completion callbacks still reconstruct the temporary layout as if seqhi were absent. With an async AH implementation selected, that makes AH copy or compare the wrong bytes on both the IPv4 and IPv6 paths. In UML repro on IPv4 AH with ESN and forced async hmac(sha1), ping fails with 100% packet loss, and the callback logs show the pre-fix drift: ah4 output_done: esn=1 err=0 icv_off=20 expected_off=24 ah4 input_done: esn=1 auth_off=20 expected_auth_off=24 icv_off=32 expected_icv_off=36 Reconstruct the callback-side layout the same way the setup path built it by skipping the ESN seqhi slot before locating the saved auth_data or ICV. Per RFC 4302, the ESN high-order 32 bits participate in the AH ICV computation, so the async callbacks must account for the seqhi slot. Post-fix, the same IPv4 AH+ESN+forced-async-hmac(sha1) UML repro shows the corrected offset (ah4 output_done: esn=1 err=0 icv_off=24 expected_off=24) and ping succeeds; net/ipv4/ah4.o and net/ipv6/ah6.o build clean at W=1. IPv6 AH+ESN was not exercised at runtime, and the change has not been tested against a real async hardware AH engine.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-46193 since 05/13/2026. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/18/2026).

The vulnerability scanner Nessus provides a plugin with the ID 327380 (Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-1924)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc3 eliminates this vulnerability. Applying the patch 0555d4f526232b3c9e3afbcd490c0c0793aefec6/729899a2aa8bda7844be0cdcd3b470f11b912eda/7db99a09b3bc87268287bc7ab5f2e7f382b5ad87/2ffaa7a94f9a4d22724364a1821735a0231d9f8d/ec54093e6a8f87e800bb6aa15eb7fc1e33faa524 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (327380). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 327380
Nessus Name: Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-1924)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc3
Patch: 0555d4f526232b3c9e3afbcd490c0c0793aefec6/729899a2aa8bda7844be0cdcd3b470f11b912eda/7db99a09b3bc87268287bc7ab5f2e7f382b5ad87/2ffaa7a94f9a4d22724364a1821735a0231d9f8d/ec54093e6a8f87e800bb6aa15eb7fc1e33faa524

Timelineinfo

05/13/2026 CVE reserved
05/28/2026 +15 days Advisory disclosed
05/28/2026 +0 days VulDB entry created
07/18/2026 +51 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46193 (🔒)
GCVE (CVE): GCVE-0-2026-46193
GCVE (VulDB): GCVE-100-366651

Entryinfo

Created: 05/28/2026 13:30
Updated: 07/18/2026 17:09
Changes: 05/28/2026 13:30 (57), 06/11/2026 00:46 (10), 07/18/2026 17:09 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!