CVE-2022-49698 [High] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: netfilter: use get_random_u32 instead of prandom bh might occur while updating per-cpu rnd_state from user context, ie. local_out path. BUG: using smp_processor_id() in preemptible [00000000] code: nginx/2725 caller is nft_ng_random_eval+0x24/0x54 [nft_numgen] Call Trace: check_preemption_disabled+0xde/0xe0 nft_ng_random_eval+0x24/0x54 [nft_numgen] Use the random driver instead, this also avoids need for local prandom state. Moreover, prandom now uses the random driver since d4150779e60f ("random32: use real rng for non-deterministic randomness"). Based on earlier patch from Pablo Neira.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.11%	0.28%	+0.17%
2	2026-04-06	0.03%	0.11%	+0.08%
3	2025-11-21	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.11%

0.28%

+0.17%

2026-04-06

0.03%

0.11%

+0.08%

2025-11-21

—

0.03%

—

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	[email protected]

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

[email protected]

OS Trackers for CVE-2022-49698

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49698 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-49698
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49698
`suse`	medium	CVE-2022-49698 severity moderate: SUSE including 46 source package names (bpftool-4.18.0-425.3.1.el8, cluster-md-kmp-default, …), 261 product×package rows across 45 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Liberty Linux 8, … (45 product lines)): Known Not Affected 241, Fixed 20.	https://www.suse.com/security/cve/CVE-2022-49698/
`ubuntu`	medium	CVE-2022-49698 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, released 135, not-affected 123, needs-triage 1, pending 1.	https://ubuntu.com/security/CVE-2022-49698

Affected software / configurations for CVE-2022-49698

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.18, < 5.10.127	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.51	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.8	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc1::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc2::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc3::::::

References for CVE-2022-49698

URL	Tags
https://git.kernel.org/stable/c/15cc30ac2a8d7185f8ebf97dd1ddd90a7c79783b	Patch
https://git.kernel.org/stable/c/6ce71f83f798be7e1ca68707fec449fbecb38852	Patch
https://git.kernel.org/stable/c/b1fd94e704571f98b21027340eecf821b2bdffba	Patch
https://git.kernel.org/stable/c/d0906b0fffc9f19bc42708ca3e84e2089088386c	Patch

URL

CVE-2022-49698 | netfilter: use get_random_u32 instead of prandom

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

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

Weakness enumeration for CVE-2022-49698

OS Trackers for CVE-2022-49698

Affected software / configurations for CVE-2022-49698

References for CVE-2022-49698