Linux Kernel up to 7.1.9 ipvlan ipvlan_init use after free

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.
9.5$5k-$25k0.30

Summaryinfo

A vulnerability labeled as very critical has been found in Linux Kernel up to 6.1.183/6.6.152/6.12.104/6.18.45/7.1.9. This affects the function ipvlan_init of the component ipvlan. Such manipulation leads to use after free. This vulnerability is traded as CVE-2026-74744. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.1.183/6.6.152/6.12.104/6.18.45/7.1.9. Affected by this issue is the function ipvlan_init of the component ipvlan. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev ipvlan devices inherit hard_header_len from phy_dev during ipvlan_init(), but leave needed_headroom and needed_tailroom set to 0. When the underlying phy_dev (or stacked lower device) requires extra headroom or tailroom for headers/trailers (e.g. macsec, ipsec, wireguard, tunnels, or veth with rx headroom), upper layers calculating packet headroom and tailroom fail to reserve sufficient space. This can result in reallocation overhead, skb headroom underflows, or KASAN slab-use-after-free crashes when dev_hard_header() / ipvlan_hard_header() prepends header data or when lower devices append tailroom. Fix this by: 1. Inheriting needed_headroom and needed_tailroom from phy_dev in ipvlan_init(). 2. Propagating needed_headroom and needed_tailroom updates to attached ipvlans in ipvlan_device_event() when receiving NETDEV_FEAT_CHANGE events.

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-74744 since 08/15/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 08/26/2026).

Upgrading to version 6.1.184, 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch af602c4d0ee548da18e2409b4b4da1079625a372/f3c17ff65f54781cde696e16a6c577615ed735aa/c0fbe31f6b20ade0465130685859faa5c86fda59/5f33188457bbcc1b11ca87084037963c516ed3d9/5c2ca77212eb38559b0353b8363b7a84f4b019dd/e16e960d55a40d36bd7c2494cc005e757dc9a1ef is able to eliminate this problem.

Once again VulDB remains the best source 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: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.184/6.6.153/6.12.105/6.18.46/7.1.10
Patch: af602c4d0ee548da18e2409b4b4da1079625a372/f3c17ff65f54781cde696e16a6c577615ed735aa/c0fbe31f6b20ade0465130685859faa5c86fda59/5f33188457bbcc1b11ca87084037963c516ed3d9/5c2ca77212eb38559b0353b8363b7a84f4b019dd/e16e960d55a40d36bd7c2494cc005e757dc9a1ef

Timelineinfo

08/15/2026 CVE reserved
08/26/2026 +11 days Advisory disclosed
08/26/2026 +0 days VulDB entry created
08/26/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-74744 (🔒)
GCVE (CVE): GCVE-0-2026-74744
GCVE (VulDB): GCVE-100-395804

Entryinfo

Created: 08/26/2026 17:04
Changes: 08/26/2026 17:04 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!