nday
CVE-2021-47497

nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from NVD's analysts
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-05-22T08:19Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells

If a cell has 'nbits' equal to a multiple of BITS_PER_BYTE the logic

*p &= GENMASK((cell->nbits%BITS_PER_BYTE) - 1, 0);

will become undefined behavior because nbits modulo BITS_PER_BYTE is 0, and we subtract one from that making a large number that is then shifted more than the number of bits that fit into an unsigned long.

UBSAN reports this problem:

UBSAN: shift-out-of-bounds in drivers/nvmem/core.c:1386:8
shift exponent 64 is too large for 64-bit type 'unsigned long'
CPU: 6 PID: 7 Comm: kworker/u16:0 Not tainted 5.15.0-rc3+ #9
Hardware name: Google Lazor (rev3+) with KB Backlight (DT)
Workqueue: events_unbound deferred_probe_work_func
Call trace:
 dump_backtrace+0x0/0x170
 show_stack+0x24/0x30
 dump_stack_lvl+0x64/0x7c
 dump_stack+0x18/0x38
 ubsan_epilogue+0x10/0x54
 __ubsan_handle_shift_out_of_bounds+0x180/0x194
 __nvmem_cell_read+0x1ec/0x21c
 nvmem_cell_read+0x58/0x94
 nvmem_cell_read_variable_common+0x4c/0xb0
 nvmem_cell_read_variable_le_u32+0x40/0x100
 a6xx_gpu_init+0x170/0x2f4
 adreno_bind+0x174/0x284
 component_bind_all+0xf0/0x264
 msm_drm_bind+0x1d8/0x7a0
 try_to_bring_up_master+0x164/0x1ac
 __component_add+0xbc/0x13c
 component_add+0x20/0x2c
 dp_display_probe+0x340/0x384
 platform_probe+0xc0/0x100
 really_probe+0x110/0x304
 __driver_probe_device+0xb8/0x120
 driver_probe_device+0x4c/0xfc
 __device_attach_driver+0xb0/0x128
 bus_for_each_drv+0x90/0xdc
 __device_attach+0xc8/0x174
 device_initial_probe+0x20/0x2c
 bus_probe_device+0x40/0xa4
 deferred_probe_work_func+0x7c/0xb8
 process_one_work+0x128/0x21c
 process_scheduled_works+0x40/0x54
 worker_thread+0x1ec/0x2a8
 kthread+0x138/0x158
 ret_from_fork+0x10/0x20

Fix it by making sure there are any bits to mask out.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 253270,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2021-47497",
  "occurred_at": "2024-05-22T08:19:44.144Z",
  "observed_at": "2026-11-13T05:37:31.591644Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "ssvc": {
      "timestamp": "2024-05-22T17:50:37.993929Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2024-05-22T08:19:44.144Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.