CVE-2022-49168 [High] | Use-After-Free in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: btrfs: do not clean up repair bio if submit fails The submit helper will always run bio_endio() on the bio if it fails to submit, so cleaning up the bio just leads to a variety of use-after-free and NULL pointer dereference bugs because we race with the endio function that is cleaning up the bio. Instead just return BLK_STS_OK as the repair function has to continue to process the rest of the pages, and the endio for the repair bio will do the appropriate cleanup for the page that it was given.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-20	0.10%	0.02%	-0.07%
2	2026-04-06	0.04%	0.10%	+0.05%
3	2025-02-27	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-20

0.10%

0.02%

-0.07%

2026-04-06

0.04%

0.10%

+0.05%

2025-02-27

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2022-49168

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49168 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-49168
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49168
`suse`	medium	CVE-2022-49168 severity moderate: SUSE including 276 source package names (amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, amazon/suse-sles-15-sp1-chost-byos-v20220127-hvm-ssd-x86_64, …), 444 product×package rows across 46 product lines (Image SLES12-SP5-Azure-BYOS, Image SLES12-SP5-Azure-HPC-BYOS, … (46 product lines)): Known Affected 231, Known Not Affected 136, Fixed 77.	https://www.suse.com/security/cve/CVE-2022-49168/
`ubuntu`	medium	CVE-2022-49168 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 149, released 124, not-affected 91, needed 42.	https://ubuntu.com/security/CVE-2022-49168

Affected software / configurations for CVE-2022-49168

Vendor	Product	Version	Raw CPE
linux	linux_kernel	< 5.10.248	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.184	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.16.19	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.17, < 5.17.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-49168

URL	Tags
https://git.kernel.org/stable/c/7170875083254b51fcc5d67f96640977083f481e	Patch
https://git.kernel.org/stable/c/8cbc3001a3264d998d6b6db3e23f935c158abd4d	Patch
https://git.kernel.org/stable/c/d1cb11fb45ebbb1e7dfe5e9038b32ea72c184b14	Patch
https://git.kernel.org/stable/c/e76c78c48902dae6fa612749f59162bca0a79e0b	Patch
https://git.kernel.org/stable/c/e7e1d15d2bd8c373cf621614ddd17971a2132713	Patch

URL

CVE-2022-49168 | btrfs: do not clean up repair bio if submit fails

Exploit prediction scoring system (EPSS) score for CVE-2022-49168

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49168

Weakness enumeration for CVE-2022-49168

OS Trackers for CVE-2022-49168

Affected software / configurations for CVE-2022-49168

References for CVE-2022-49168