LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47527: serial: core: fix transmit-buffer reset and memleak

In the Linux kernel, the following vulnerability has been resolved: serial: core: fix transmit-buffer reset and memleak Commit 761ed4a94582 ("tty: serial_core: convert uart_close to use tty_port_close") converted serial core to use tty_port_close() but failed to notice that the transmit buffer still needs to be freed on final close. Not freeing the transmit buffer means that the buffer is no longer cleared on next open so that any ioctl() waiting for the buffer to drain might wait indefinitely (e.g. on termios changes) or that stale data can end up being transmitted in case tx is restarted. Furthermore, the buffer of any port that has been opened would leak on driver unbind. Note that the port lock is held when clearing the buffer pointer due to the ldisc race worked around by commit a5ba1d95e46e ("uart: fix race between uart_put_char() and uart_shutdown()"). Also note that the tty-port shutdown() callback is not called for console ports so it is not strictly necessary to free the buffer page after releasing the lock (cf. d72402145ace ("tty/serial: do not free trasnmit buffer page under port lock")).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects serial port handling. A transmit buffer was not freed on final close, which could leave old data for later transmission, cause some operations to wait indefinitely, or leak memory after driver unbind. The sources do not provide CVSS, attack vector, or active exploitation evidence.

Executive priority

Treat as a targeted kernel maintenance issue, not an internet-scale emergency based on available evidence. Prioritize patching where serial ports support operations, embedded devices, appliances, or management consoles.

Technical view

A serial_core change to use tty_port_close() missed freeing the UART transmit buffer on final close. Consequences described by the kernel source include uncleared buffers on reopen, ioctl waits for drain that may hang, stale transmitted data if TX restarts, and leaked buffers for opened ports on driver unbind.

Likely exposure

Exposure is most likely on Linux systems running affected kernel branches that use serial or UART ports. The provided affected data references Linux 4.9, 4.14, 4.19, 5.4, 5.10, 5.15, and 5.16 ranges, but distribution backports require vendor confirmation.

Exploitation context

The bundle does not show KEV listing, public exploitation, or a remote attack path. The described impacts are operational reliability, stale data transmission, and kernel memory leakage tied to serial port lifecycle handling.

Researcher notes

The evidence is limited to the CVE record and upstream stable fix references. No CWE, CVSS, exploit status, or distribution package matrix is included. Avoid assuming exploitability beyond the stated serial buffer lifecycle impacts.

Mitigation direction

  • Apply vendor kernel updates containing the stable serial_core fixes.
  • Confirm distribution backports instead of relying only on upstream version numbers.
  • Prioritize systems using serial consoles, UART devices, or serial-connected operational hardware.
  • Monitor vendor advisories for branch-specific fixed package versions.

Validation and detection

  • Inventory Linux kernel versions across systems using serial or UART ports.
  • Check whether installed kernel packages include the linked stable commits or vendor backports.
  • Review logs for serial port hangs, termios change stalls, or driver unbind issues.
  • Validate patched kernels in staging with representative serial device workflows.
Prepared
Confidence
medium
Sources
9

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-47527 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
8Source 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
LinuxLinux761ed4a94582ab291aa24dcbea4e01e8936488c8, 761ed4a94582ab291aa24dcbea4e01e8936488c8, 761ed4a94582ab291aa24dcbea4e01e8936488c8, 761ed4a94582ab291aa24dcbea4e01e8936488c8, 761ed4a94582ab291aa24dcbea4e01e8936488c8, 761ed4a94582ab291aa24dcbea4e01e8936488c8, 761ed4a94582ab291aa24dcbea4e01e8936488c8unaffected
LinuxLinux4.9, 0, 4.9.292, 4.14.257, 4.19.220, 5.4.164, 5.10.84, 5.15.7, 5.16affected
Weakness

CWE details

No CWE listed

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