Bug 1991722 (CVE-2021-38160) - CVE-2021-38160 kernel: data corruption or loss can be triggered by an untrusted device that supplies a buf->len value exceeding the buffer size in drivers/char/virtio_console.c
Summary: CVE-2021-38160 kernel: data corruption or loss can be triggered by an untrust...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2021-38160
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1991723 1991947 1991948 1991949 1991950 1991951
Blocks: 1991724
TreeView+ depends on / blocked
 
Reported: 2021-08-09 19:46 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-04-17 21:32 UTC (History)
45 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
This CVE is being DISPUTED (*) by Red Hat with a note that the cited data corruption is not a vulnerability in any existing use case; the length validation was added solely for robustness in the face of anomalous host OS behavior. (*) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38160
Clone Of:
Environment:
Last Closed: 2021-09-03 10:59:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-08-09 19:46:30 UTC
This CVE is being DISPUTED (*) by Red Hat with a note that the cited data corruption is not a vulnerability in any existing use case; the length validation was added solely for robustness in the face of anomalous host OS behavior. 

(*) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38160

Reference and upstream patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d00d8da5869a2608e97cfede094dfc5e11462a46

Comment 1 Guilherme de Almeida Suckevicz 2021-08-09 19:47:15 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1991723]

Comment 5 Justin M. Forbes 2021-08-10 18:36:32 UTC
This was fixed for Fedora with the 5.13.4 stable kernel updates.


Note You need to log in before you can comment on or make changes to this bug.