dbcve.org
Linux KernelOperating system · Linux

CVE-2022-48659

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-28
Fix available
A fix is available. Upgrade to 4.9.330 / 4.14.295 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: mm/slub: fix to return errno if kmalloc() fails In create_unique_id(), kmalloc(, GFP_KERNEL) can fail due to out-of-memory, if it fails, return errno correctly rather than triggering panic via BUG_ON(); kernel BUG at mm/slub.c:5893! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Call trace: sysfs_slab_add+0x258/0x260 mm/slub.c:5973 __kmem_cache_create+0x60/0x118 mm/slub.c:4899 create_cache mm/slab_common.c:229 [inline] kmem_cache_create_usercopy+0x19c/0x31c mm/slab_common.c:335 kmem_cache_create+0x1c/0x28 mm/slab_common.c:390 f2fs_kmem_cache_create fs/f2fs/f2fs.h:2766 [inline] f2fs_init_xattr_caches+0x78/0xb4 fs/f2fs/xattr.c:808 f2fs_fill_super+0x1050/0x1e0c fs/f2fs/super.c:4149 mount_bdev+0x1b8/0x210 fs/super.c:1400 f2fs_mount+0x44/0x58 fs/f2fs/super.c:4512 legacy_get_tree+0x30/0x74 fs/fs_context.c:610 vfs_get_tree+0x40/0x140 fs/super.c:1530 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040 path_mount+0x358/0x914 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 2.6.22, < 4.9.330>= 4.10, < 4.14.295>= 4.15, < 4.19.260>= 4.20, < 5.4.215>= 5.5, < 5.10.146>= 5.11, < 5.15.71>= 5.16, < 5.19.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.9.330 / 4.14.295 / 4.19.260 or later
Fixed in 4.9.3304.14.2954.19.260
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel version 4.9.330+ (if on 4.9.x), 4.14.295+ (if on 4.14.x), 4.19.260+ (if on 4.19.x), or 5.4.215+ (if on 5.0-5.3.x)

  1. Check the current running kernel version using `uname -r` or `cat /proc/version` to determine which kernel branch you are on
  2. Identify the appropriate fixed version based on your current branch: for 4.9.x upgrade to >= 4.9.330, for 4.14.x upgrade to >= 4.14.295, for 4.19.x upgrade to >= 4.19.260, for 5.0-5.3.x upgrade to >= 5.4.215
  3. For distribution-specific kernels (e.g., Ubuntu, Red Hat, Debian), use your distribution's package manager to upgrade (e.g., `apt-get update && apt-get upgrade` for Debian/Ubuntu, or `yum update` for RHEL/CentOS)
  4. For custom/unpatched kernels, obtain a kernel source or binary from your distribution vendor or kernel.org that includes the fix commit 016b150992eebc32c4a18f783cf2bb6e2545a3d9
  5. Reboot the system into the upgraded kernel to apply the fix
  6. Verify the fix is applied by checking the kernel version and confirming the BUG_ON in mm/slub.c create_unique_id() has been replaced with proper error handling
Caveat Kernel upgrades may require driver/module recompilation and could introduce compatibility issues with older userspace tools; ensure backup and test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-48659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-48659 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data