CVE-2026-74255
Description
A flaw was found in the Linux kernel's Transparent Inter-Process Communication (TIPC) module. This use-after-free vulnerability occurs when the tipc_disable_l2_media() function calls synchronize_net() before properly invalidating a media pointer. This timing issue allows concurrent readers to access a memory region after it has been freed, which can lead to system instability or a denial of service.
Statement
A race in the TIPC L2 bearer disable path can leave b.media_ptr visible to RCU readers while the underlying net_device is being detached and released. A concurrent reader in tipc_l2_send_msg can then use a stale device pointer and reach a slab use after free in ipvlan_hard_header, causing at least a kernel crash. For the CVSS the PR:L is used for the paranoid score because reduced capability root, container root, or delegated CAP_NET_ADMIN may be enough to control TIPC bearer state in some deployments. The issue is not proven to be directly network reachable by packet traffic alone, but network activity can participate in the race once bearer teardown is triggered. Impact is at least local denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to a race based UAF in kernel networking code.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | N/A | 9.8 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.