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

In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: don't delete error page from pagecache This change is very similar to the change that was made for shmem [1], and it solves the same problem but for HugeTLBFS instead. Currently, when poison is found in a HugeTLB page, the page is removed from the page cache. That means that attempting to map or read that hugepage in the future will result in a new hugepage being allocated instead of notifying the user that the page was poisoned. As [1] states, this is effectively memory corruption. The fix is to leave the page in the page cache. If the user attempts to use a poisoned HugeTLB page with a syscall, the syscall will fail with EIO, the same error code that shmem uses. For attempts to map the page, the thread will get a BUS_MCEERR_AR SIGBUS. [1]: commit a76054266661 ("mm: shmem: don't truncate page if memory failure happens")

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.03%	0.16%	+0.12%
2	2026-06-14	0.17%	0.03%	-0.13%
3	2026-06-10	—	0.17%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.03%

0.16%

+0.12%

2026-06-14

0.17%

0.03%

-0.13%

2026-06-10

—

0.17%

—

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-49828

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49828 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1.	https://security-tracker.debian.org/tracker/CVE-2022-49828
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49828
`suse`	medium	CVE-2022-49828 severity moderate: SUSE including 25 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 123 product×package rows across 25 product lines (SUSE Linux Enterprise High Availability Extension 15 SP7, SUSE Linux Enterprise Live Patching 12 SP5, … (25 product lines)): Known Not Affected 106, Will Not Fix 17.	https://www.suse.com/security/cve/CVE-2022-49828/
`ubuntu`	medium	CVE-2022-49828 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 150, released 116, not-affected 97, needed 42, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49828

Affected software / configurations for CVE-2022-49828

Vendor	Product	Version	Raw CPE
linux	linux_kernel	< 5.15.80	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.10	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-49828

URL	Tags
https://git.kernel.org/stable/c/30571f28bb35c826219971c63bcf60d2517112ed	Patch
https://git.kernel.org/stable/c/8625147cafaa9ba74713d682f5185eb62cb2aedb	Patch
https://git.kernel.org/stable/c/ec667443b2dbc6cdbbac4073e51a17733158ec6a	Patch

URL

CVE-2022-49828 | hugetlbfs: don't delete error page from pagecache

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

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

Weakness enumeration for CVE-2022-49828

OS Trackers for CVE-2022-49828

Affected software / configurations for CVE-2022-49828

References for CVE-2022-49828