LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14283: In the Linux kernel before 5.2.3, set_geometry in drivers/block/floppy.c does not validate the sect and hea...

In the Linux kernel before 5.2.3, set_geometry in drivers/block/floppy.c does not validate the sect and head fields, as demonstrated by an integer overflow and out-of-bounds read. It can be triggered by an unprivileged local user when a floppy disk has been inserted. NOTE: QEMU creates the floppy device by default.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a local Linux kernel flaw in the floppy disk driver. A normal local user could trigger unsafe handling of floppy geometry fields on vulnerable kernels when a floppy disk is present. The sources do not show remote exploitation or active exploitation, but QEMU-created default floppy devices make virtual machines worth checking.

Executive priority

Prioritize normal patch-cycle remediation, with faster handling for multi-user Linux systems and VM fleets using older QEMU templates. The available evidence does not justify emergency remote-compromise response, but kernel bugs can affect system stability and isolation.

Technical view

Linux kernels before 5.2.3 did not validate sect and head fields in drivers/block/floppy.c set_geometry, allowing integer overflow and out-of-bounds read conditions. The CVE says an unprivileged local user can trigger it when a floppy disk has been inserted. The upstream fix is commit da99466ac243f15fbba65bd261bfc75ffa1532b6.

Likely exposure

Exposure is mainly Linux hosts or virtual machines running vulnerable kernels with floppy support present. QEMU-created floppy devices are specifically called out, so older VM templates may be relevant. Systems without local untrusted users or without usable floppy devices appear less exposed based on the provided sources.

Exploitation context

The source bundle supports local, unprivileged triggering under specific floppy-device conditions. It does not cite remote exploitation, public weaponization, or CISA KEV listing. Treat this as a local kernel hardening and patch hygiene issue unless vendor guidance for your distribution indicates higher urgency.

Researcher notes

Key constraints are local access, vulnerable kernel, floppy driver path, and inserted or available floppy media. The CVE metadata has no CVSS or CWE details, so severity confidence is limited. Vendor advisories confirm broad distribution handling through kernel updates.

Mitigation direction

  • Apply vendor kernel security updates from your Linux distribution.
  • Upgrade to a kernel containing the Linux 5.2.3 floppy driver fix or vendor backport.
  • Review QEMU VM templates for unnecessary floppy devices.
  • Follow Debian, Ubuntu, Slackware, openSUSE, or other applicable vendor advisories.
  • Prioritize shared systems where untrusted users have local access.

Validation and detection

  • Inventory Linux kernel versions across hosts and VM images.
  • Check whether kernels include commit da99466ac243 or a vendor backport.
  • Identify QEMU VMs with floppy devices enabled.
  • Confirm distribution advisory packages are installed.
  • Review local-user exposure on affected Linux systems.
Prepared
Confidence
high
Sources
10

Public sources used

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-2019-14283 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
0Timeline events
0ADP providers
17Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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