CVE-2022-49401: mm/page_owner: use strscpy() instead of strlcpy()
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 5cd9900a1ac8b0a4ff3cd97d4d77b7711be435bf, cd8c1fd8cdd14158f2d8bea2d1bfe8015dccfa3a.
Low priority for now. Upgrade to Linux Linux 5cd9900a1ac8b0a4ff3cd97d4d77b7711be435bf, cd8c1fd8cdd14158f2d8bea2d1bfe8015dccfa3a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: mm/page_owner: use strscpy() instead of strlcpy() current->comm[] is not a string (no guarantee for a zero byte in it). strlcpy(s1, s2, l) is calling strlen(s2), potentially causing out-of-bound access, as reported by syzbot: detected buffer overflow in __fortify_strlen ------------[ cut here ]------------ kernel BUG at lib/string_helpers.c:980! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 4087 Comm: dhcpcd-run-hooks Not tainted 5.18.0-rc3-syzkaller-01537-g20b87e7c29df #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:fortify_panic+0x18/0x1a lib/string_helpers.c:980 Code: 8c e8 c5 ba e1 fa e9 23 0f bf fa e8 0b 5d 8c f8 eb db 55 48 89 fd e8 e0 49 40 f8 48 89 ee 48 c7 c7 80 f5 26 8a e8 99 09 f1 ff <0f> 0b e8 ca 49 40 f8 48 8b 54 24 18 4c 89 f1 48 c7 c7 00 00 27 8a RSP: 0018:ffffc900000074a8 EFLAGS: 00010286 RAX: 000000000000002c RBX: ffff88801226b728 RCX: 0000000000000000 RDX: ffff8880198e0000 RSI: ffffffff81600458 RDI: fffff52000000e87 RBP: ffffffff89da2aa0 R08: 000000000000002c R09: 0000000000000000 R10: ffffffff815fae2e R11: 0000000000000000 R12: ffff88801226b700 R13: ffff8880198e0830 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f5876ad6ff8 CR3: 000000001a48c000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600 Call Trace: <IRQ> __fortify_strlen include/linux/fortify-string.h:128 [inline] strlcpy include/linux/fortify-string.h:143 [inline] __set_page_owner_handle+0x2b1/0x3e0 mm/page_owner.c:171 __set_page_owner+0x3e/0x50 mm/page_owner.c:190 prep_new_page mm/page_alloc.c:2441 [inline] get_page_from_freelist+0xba2/0x3e00 mm/page_alloc.c:4182 __alloc_pages+0x1b2/0x500 mm/page_alloc.c:5408 alloc_pages+0x1aa/0x310 mm/mempolicy.c:2272 alloc_slab_page mm/slub.c:1799 [inline] allocate_slab+0x26c/0x3c0 mm/slub.c:1944 new_slab mm/slub.c:2004 [inline] ___slab_alloc+0x8df/0xf20 mm/slub.c:3005 __slab_alloc.constprop.0+0x4d/0xa0 mm/slub.c:3092 slab_alloc_node mm/slub.c:3183 [inline] slab_alloc mm/slub.c:3225 [inline] __kmem_cache_alloc_lru mm/slub.c:3232 [inline] kmem_cache_alloc+0x360/0x3b0 mm/slub.c:3242 dst_alloc+0x146/0x1f0 net/core/dst.c:92
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.18 and later · before 5.18.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.18affected
- 865ed6a3278654ce4a55eb74c5283eeb82ad4699 and later · before 5cd9900a1ac8b0a4ff3cd97d4d77b7711be435bfaffected · git
- 865ed6a3278654ce4a55eb74c5283eeb82ad4699 and later · before cd8c1fd8cdd14158f2d8bea2d1bfe8015dccfa3aaffected · git
- before 5.18not affected · semver
- 5.18.3 and later · up to and including 5.18.*not affected · semver
- 5.19 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.18.5-1 | 5.18.5-1 |
| Red Hat:enterprise_linux:8::baseos | bpftool | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | bpftool-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-abi-stablelists | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-core | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-core | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-devel | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules-extra | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-aarch64 | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-ppc64le | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-s390x | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-devel | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-doc | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules-extra | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools-libs | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
+11
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49399Feb 26, 2025 · tty: goldfish: Use tty_port_destroy() to destroy port22Monitor
- ← EarlierCVE-2022-49400Feb 26, 2025 · md: Don't set mddev private to NULL in raid0 pers->free22Monitor
- Later →CVE-2022-49402Feb 26, 2025 · ftrace: Clean up hash direct_functions on register failures22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5cd9900a1ac8b0a4ff3cd97d4d77b7711be435bf | Vendor (CNA) |
| Linux Linux | cd8c1fd8cdd14158f2d8bea2d1bfe8015dccfa3a | Vendor (CNA) |
| debian:linux | 5.18.5-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-513.5.1.el8_9 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.