Bug 1927938 - There is an inconsequential (to date) 1 byte buffer overflow in vdo user tools.
Summary: There is an inconsequential (to date) 1 byte buffer overflow in vdo user tools.
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: 8.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: corwin
QA Contact: Filip Suba
Depends On:
TreeView+ depends on / blocked
Reported: 2021-02-11 21:31 UTC by corwin
Modified: 2021-11-10 06:37 UTC (History)
4 users (show)

Fixed In Version: vdo-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-09 19:28:28 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4359 0 None None None 2021-11-09 19:28:38 UTC

Description corwin 2021-02-11 21:31:31 UTC
Description of problem:

When setting up for file based access to a VDO's backing device, the file name is copied into a buffer via strcpy(). That buffer is allocated 1 byte too small to contain the terminating \0.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run any VDO user tool under valgrind.

Actual results:
Valgrind reports: "Invalid write of size 1"

Expected results:
Valgrind does not report any invalid writes.

Additional info:
To date, we have seen no consequences from this issue.

Comment 5 Filip Suba 2021-07-30 09:01:27 UTC
Verified with vdo-

Comment 8 errata-xmlrpc 2021-11-09 19:28:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (kmod-kvdo bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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