CVE-2022-49849 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix match incorrectly in dev_args_match_device syzkaller found a failed assertion: assertion failed: (args->devid != (u64)-1) || args->missing, in fs/btrfs/volumes.c:6921 This can be triggered when we set devid to (u64)-1 by ioctl. In this case, the match of devid will be skipped and the match of device may succeed incorrectly. Patch 562d7b1512f7 introduced this function which is used to match device. This function contains two matching scenarios, we can distinguish them by checking the value of args->missing rather than check whether args->devid and args->uuid is default value.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-09	0.02%	0.21%	+0.20%
2	2025-05-02	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-09

0.02%

0.21%

+0.20%

2025-05-02

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-49849

vendor	priority	summary	link
`debian`	unimportant	CVE-2022-49849 unimportant 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-49849
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49849
`suse`	medium	CVE-2022-49849 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 264 product×package rows across 51 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 15 SP7, … (51 product lines)): Known Not Affected 264.	https://www.suse.com/security/cve/CVE-2022-49849/
`ubuntu`	medium	CVE-2022-49849 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 146, not-affected 143, released 116, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49849

Affected software / configurations for CVE-2022-49849

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.15.54, < 5.15.79	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.9	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc1::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc2::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc3::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc4::::::

References for CVE-2022-49849

URL	Tags
https://git.kernel.org/stable/c/0fca385d6ebc3cabb20f67bcf8a71f1448bdc001	Patch
https://git.kernel.org/stable/c/bc6c127c377010f136360552ebf91c2723081c1b	Patch
https://git.kernel.org/stable/c/c9fe4719c662e0af17eea723cf345e37719fd3c9	Patch

URL

CVE-2022-49849 | btrfs: fix match incorrectly in dev_args_match_device

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

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

Weakness enumeration for CVE-2022-49849

OS Trackers for CVE-2022-49849

Affected software / configurations for CVE-2022-49849

References for CVE-2022-49849