PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-74675 Linux CVE debrief

A vulnerability in the Linux kernel has been resolved, which could potentially allow local attackers to escalate privileges. The issue arises from a race condition in the vt subsystem, specifically in the kbd_keycode function, where a tty reference is not properly stabilized, leading to a potential use-after-free vulnerability. This vulnerability affects Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems, who should assess their exposure and apply the patch or update to a fixed version. The vulnerability has a CVSS score of 7.8 and is considered HIGH severity. The CVE record and source item provide details about the vulnerabil

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-22
Original CVE updated
2026-10-16
Advisory published
2026-08-22
Advisory updated
2026-10-16

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems should assess their exposure and apply the patch or update to a fixed version.

Why it matters

CVE-2026-74675 is a Linux kernel vulnerability that could allow local attackers to escalate privileges. It arises from a race condition in the vt subsystem, specifically in the kbd_keycode function. Linux kernel developers, maintainers, and users should assess exposure and apply patches or updates to prevent exploitation.

  • Local privilege escalation is possible if an attacker can trigger the race condition.
  • System crashes or instability may occur if the vulnerability is exploited.
  • Verification of affected versions and application of patches is necessary to prevent exploitation.
  • Monitoring system logs for potential exploitation attempts is recommended.

Technical summary

The vulnerability is caused by a race condition in the vt subsystem, specifically in the kbd_keycode function. This function reads vc->port.tty without acquiring a tty reference, which can lead to a use-after-free vulnerability when con_shutdown() clears port.tty under a different lock. The fix involves using tty_port_tty_get()/tty_kref_put() to hold a proper reference for the duration the tty pointer is needed.

Defensive priority

Medium

Recommended defensive actions

  • Review and apply the patch provided by the Linux kernel maintainers.
  • Update Linux kernel to a version that includes the fix.
  • Monitor system logs for potential exploitation attempts.
  • Perform a thorough review of system configurations and apply compensating controls if necessary.
  • Verify the integrity of affected systems and ensure that all necessary patches are applied.
  • Track exceptions and retest remediated assets to ensure that the vulnerability is fully resolved.
  • Conduct a comprehensive asset inventory to identify all affected systems and prioritize remediation efforts.

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description and affected versions. However, the corpus does not establish specific exploitation or impact details, requiring verification from official sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-74675 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-74675

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-74675 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74675

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • vt: stabilize tty reference in kbd_keycode with tty_port_tty_get

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/74xxx/CVE-2026-74675.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b84fd400f80adf4d1c88fbce50ae1cf2f8119e65

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/38400673c9bfb39cfc87539e1a072087e98f4e4f

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/cab5a342f0589334046741006d8a280514f94235

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/38a0aa593ebc275aea6f79534d07f44e43768ce6

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/3f6b1d3fcfc26dc3fc85262f753439df93b055b4

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b664592e9ba8c47c9e23408db7ba52eb9f946c8a

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/cc4a1a2ce0c58eafd477effb055863935260ddc1

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.