CVE-2026-90334
Description
A flaw was found in the Linux kernel's tty subsystem. When a character device (cdev) is added and fails, a pointer to the device's memory is not properly cleared. This can lead to a 'use-after-free' vulnerability, where the system attempts to access memory that has already been released. A local attacker could potentially exploit this to cause a system crash (denial of service) or, in some scenarios, execute arbitrary code.
Statement
A use after free can occur in the tty device registration path when tty_cdev_add drops the cdev reference after cdev_add fails but leaves driver cdevs index pointing to freed memory. A later tty_unregister_device call can pass this stale pointer to cdev_del, which turns the failed registration path into a kernel memory safety issue. For the CVSS the PR:L is used in the paranoid score because a local user may be able to influence failure timing indirectly through memory pressure or delegated device management, although reliable triggering normally requires privileged driver or device lifecycle control. The issue is not network reachable and is triggered through local device registration and unregister paths. Impact is at least local denial of service via kernel crash and in the worst defensible case may include confidentiality and integrity impact or privilege escalation due to kernel UAF memory corruption.
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 | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.