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

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC There is a small race window at snd_pcm_oss_sync() that is called from OSS PCM SNDCTL_DSP_SYNC ioctl; namely the function calls snd_pcm_oss_make_ready() at first, then takes the params_lock mutex for the rest. When the stream is set up again by another thread between them, it leads to inconsistency, and may result in unexpected results such as NULL dereference of OSS buffer as a fuzzer spotted recently. The fix is simply to cover snd_pcm_oss_make_ready() call into the same params_lock mutex with snd_pcm_oss_make_ready_locked() variant.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.06%	0.03%	-0.03%
2	2025-11-18	0.04%	0.06%	+0.02%
3	2025-03-03	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.06%

0.03%

-0.03%

2025-11-18

0.04%

0.06%

+0.02%

2025-03-03

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. 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.0	3.6	[email protected]
4.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. 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.0	3.6	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.7

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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.0

3.6

[email protected]

4.7

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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.0

3.6

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

OS Trackers for CVE-2022-49733

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49733 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-49733
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2022-49733
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-49733/
`ubuntu`	medium	CVE-2022-49733 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, released 157, ignored 147, not-affected 100, needed 1, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49733

Affected software / configurations for CVE-2022-49733

Vendor	Product	Version	Raw CPE
linux	linux_kernel	< 5.4.215	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.148	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.68	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.19.9	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.0	cpe:2.3:o:linux:linux_kernel:6.0:rc1::::::
linux	linux_kernel	6.0	cpe:2.3:o:linux:linux_kernel:6.0:rc2::::::
linux	linux_kernel	6.0	cpe:2.3:o:linux:linux_kernel:6.0:rc3::::::
linux	linux_kernel	6.0	cpe:2.3:o:linux:linux_kernel:6.0:rc4::::::

References for CVE-2022-49733

URL	Tags
https://git.kernel.org/stable/c/4051324a6dafd7053c74c475e80b3ba10ae672b0	Patch
https://git.kernel.org/stable/c/723ac5ab2891b6c10dd6cc78ef5456af593490eb	Patch
https://git.kernel.org/stable/c/8015ef9e8a0ee5cecfd0cb6805834d007ab26f86	Patch
https://git.kernel.org/stable/c/8423f0b6d513b259fdab9c9bf4aaa6188d054c2d	Patch
https://git.kernel.org/stable/c/fce793a056c604b41a298317cf704dae255f1b36	Patch

URL

CVE-2022-49733 | ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC

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

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

Weakness enumeration for CVE-2022-49733

OS Trackers for CVE-2022-49733

Affected software / configurations for CVE-2022-49733

References for CVE-2022-49733