CVE-2021-47119
What it is
In the Linux kernel, the following vulnerability has been resolved: ext4: fix memory leak in ext4_fill_super Buffer head references must be released before calling kill_bdev(); otherwise the buffer head (and its page referenced by b_data) will not be freed by kill_bdev, and subsequently that bh will be leaked. If blocksizes differ, sb_set_blocksize() will kill current buffers and page cache by using kill_bdev(). And then super block will be reread again but using correct blocksize this time. sb_set_blocksize() didn't fully free superblock page and buffer head, and being busy, they were not freed and instead leaked. This can easily be reproduced by calling an infinite loop of: systemctl start <ext4_on_lvm>.mount, and systemctl stop <ext4_on_lvm>.mount ... since systemd creates a cgroup for each slice which it mounts, and the bh leak get amplified by a dying memory cgroup that also never gets freed, and memory consumption is much more easily noticed.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-401
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.43
- Linux Kernel < 5.12.10
- Linux Kernel 5.13
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2021-47119.md and follow it. Check whether this project is affected by CVE-2021-47119. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/01d349a481f0591230300a9171330136f9159bcd
- https://git.kernel.org/stable/c/1385b23396d511d5233b8b921ac3058b3f86a5e1
- https://git.kernel.org/stable/c/afd09b617db3786b6ef3dc43e28fe728cfea84df
- https://git.kernel.org/stable/c/01d349a481f0591230300a9171330136f9159bcd
- https://git.kernel.org/stable/c/1385b23396d511d5233b8b921ac3058b3f86a5e1
- https://git.kernel.org/stable/c/afd09b617db3786b6ef3dc43e28fe728cfea84df
References
- https://git.kernel.org/stable/c/01d349a481f0591230300a9171330136f9159bcd
- https://git.kernel.org/stable/c/1385b23396d511d5233b8b921ac3058b3f86a5e1
- https://git.kernel.org/stable/c/afd09b617db3786b6ef3dc43e28fe728cfea84df
- https://git.kernel.org/stable/c/01d349a481f0591230300a9171330136f9159bcd
- https://git.kernel.org/stable/c/1385b23396d511d5233b8b921ac3058b3f86a5e1
- https://git.kernel.org/stable/c/afd09b617db3786b6ef3dc43e28fe728cfea84df