LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46904: net: hso: fix null-ptr-deref during tty device unregistration

In the Linux kernel, the following vulnerability has been resolved: net: hso: fix null-ptr-deref during tty device unregistration Multiple ttys try to claim the same the minor number causing a double unregistration of the same device. The first unregistration succeeds but the next one results in a null-ptr-deref. The get_free_serial_index() function returns an available minor number but doesn't assign it immediately. The assignment is done by the caller later. But before this assignment, calls to get_free_serial_index() would return the same minor number. Fix this by modifying get_free_serial_index to assign the minor number immediately after one is found to be and rename it to obtain_minor() to better reflect what it does. Similary, rename set_serial_by_index() to release_minor() and modify it to free up the minor number of the given hso_serial. Every obtain_minor() should have corresponding release_minor() call.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability flaw in the hso network/tty driver. Multiple tty devices can claim the same minor number, causing double unregistration and a null pointer dereference. Based on the supplied sources, the likely business impact is denial of service on systems using this driver, not confirmed data theft or remote compromise.

Executive priority

Schedule remediation through normal kernel patch cycles, with faster handling for systems using hso hardware or showing related crashes. Current evidence supports moderate urgency because active exploitation and confidentiality impact are not established.

Technical view

The bug is in hso tty minor-number allocation. get_free_serial_index returned an available minor without reserving it, so concurrent callers could reuse it. The upstream fix reserves the minor immediately via obtain_minor and pairs it with release_minor during cleanup. The source bundle lists Linux as affected and provides stable kernel fix commits.

Likely exposure

Exposure appears limited to Linux systems with the hso driver and relevant tty device handling. The supplied data does not identify distributions, default configurations, cloud images, or appliances. Confirm impact through kernel package provenance and whether hso is present or loaded.

Exploitation context

The bundle does not cite active exploitation, public exploit availability, or KEV listing. Treat this as an availability risk until vendor advisories or fleet evidence show broader exposure.

Researcher notes

The key issue is reservation timing for tty minor allocation, not an authentication or memory disclosure primitive in the supplied text. Research should focus on affected kernel branches, distro backports, driver reachability, and crash reproducibility without assuming remote exploitability.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable fixes.
  • Check distribution advisories for backported fixes and supported package names.
  • Prioritize systems where the hso driver is present or loaded.
  • If updates are unavailable, follow vendor guidance for temporary driver exposure reduction.

Validation and detection

  • Inventory kernel versions and package build provenance across Linux assets.
  • Check whether the hso module is installed, enabled, or loaded.
  • Map installed kernels to vendor advisories or referenced stable commits.
  • Review kernel logs for hso-related null pointer dereference crashes.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-46904 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux72dc1c096c7051a48ab1dbb12f71976656b55eb5, 72dc1c096c7051a48ab1dbb12f71976656b55eb5, 72dc1c096c7051a48ab1dbb12f71976656b55eb5, 72dc1c096c7051a48ab1dbb12f71976656b55eb5, 72dc1c096c7051a48ab1dbb12f71976656b55eb5, 72dc1c096c7051a48ab1dbb12f71976656b55eb5, 72dc1c096c7051a48ab1dbb12f71976656b55eb5, 72dc1c096c7051a48ab1dbb12f71976656b55eb5unaffected
LinuxLinux2.6.27, 0, 4.4.268, 4.9.268, 4.14.232, 4.19.187, 5.4.112, 5.10.30, 5.11.14, 5.12affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.