Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2022-49771

medium

In the Linux kernel, the following vulnerability has been resolved: dm ioctl: fix misbehavior if list_versions races with module loading __list_versions will…

Vendor / product: Linux — linux kernel

In the Linux kernel, the following vulnerability has been resolved: dm ioctl: fix misbehavior if list_versions races with module loading __list_versions will first estimate the required space using the "dm_target_iterate(list_version_get_needed, &needed)" call and then will fill the space using the "dm_target_iterate(list_version_get_info, &iter_info)" call. Each of these calls locks the targets using the "down_read(&_lock)" and "up_read(&_lock)" calls, however between the first and second "dm_target_iterate" there is no lock held and the target modules can be loaded at this point, so the second "dm_target_iterate" call may need more space than what was the first "dm_target_iterate" returned. The code tries to handle this overflow (see the beginning of list_version_get_info), however this handling is incorrect. The code sets "param->data_size = param->data_start + needed" and "iter_info.end = (char *)vers+len" - "needed" is the size returned by the first dm_target_iterate call; "len" is the size of the buffer allocated by userspace. "len" may be greater than "needed"; in this case, the code will write up to "len" bytes into the buffer, however param->data_size is set to "needed", so it may write data past the param->data_size value. The ioctl interface copies only up to param->data_size into userspace, thus part of the result will be truncated. Fix this bug by setting "iter_info.end = (char *)vers + needed;" - this guarantees that the second "dm_target_iterate" call will write only up to the "needed" buffer and it will exit with "DM_BUFFER_FULL_FLAG" if it overflows the "needed" space - in this case, userspace will allocate a larger buffer and retry. Note that there is also a bug in list_version_get_needed - we need to add "strlen(tt->name) + 1" to the needed size, not "strlen(tt->name)".

CVSS
4.7
4.7 (CVSS v3.1)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-05-01 15:16
Modified: 2026-11-05 20:17
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-05 20:22 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel <4.9.334, ≥4.10 <4.14.300, ≥4.15 <4.19.267, ≥4.20 <5.4.225, ≥5.5 <5.10.156, ≥5.11 <5.15.80

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/0c8d4112df329bf3dfbf27693f918c3b08676538
Patch / mitigation: https://git.kernel.org/stable/c/3a1c35d72dc0b34d1e746ed705790c0f630aa427
Patch / mitigation: https://git.kernel.org/stable/c/4fe1ec995483737f3d2a14c3fe1d8fe634972979
Patch / mitigation: https://git.kernel.org/stable/c/5398b8e275bf81a2517b327d216c0f37ac9ac5ae
Patch / mitigation: https://git.kernel.org/stable/c/6a818db0d5aecf80d4ba9e10ac153f60adc629ca
Patch / mitigation: https://git.kernel.org/stable/c/6ffce7a92ef5c68f7e5d6f4d722c2f96280c064b
Patch / mitigation: https://git.kernel.org/stable/c/b545c0e1e4094d4de2bdfe9a3823f9154b0c0005
Patch / mitigation: https://git.kernel.org/stable/c/f59f5a269ca5e43c567aca7f1f52500a0186e9b7

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 20:22 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs