CVE-2023-53768 Details
Description
In the Linux kernel, the following vulnerability has been resolved: regmap-irq: Fix out-of-bounds access when allocating config buffers When allocating the 2D array for handling IRQ type registers in regmap_add_irq_chip_fwnode(), the intent is to allocate a matrix with num_config_bases rows and num_config_regs columns. This is currently handled by allocating a buffer to hold a pointer for each row (i.e. num_config_bases). After that, the logic attempts to allocate the memory required to hold the register configuration for each row. However, instead of doing this allocation for each row (i.e. num_config_bases allocations), the logic erroneously does this allocation num_config_regs number of times. This scenario can lead to out-of-bounds accesses when num_config_regs is greater than num_config_bases. Fix this by updating the terminating condition of the loop that allocates the memory for holding the register configuration to allocate memory only for each row in the matrix. Amit Pundir reported a crash that was occurring on his db845c device due to memory corruption (see "Closes" tag for Amit's report). The KASAN report below helped narrow it down to this issue: [ 14.033877][ T1] ================================================================== [ 14.042507][ T1] BUG: KASAN: invalid-access in regmap_add_irq_chip_fwnode+0x594/0x1364 [ 14.050796][ T1] Write of size 8 at addr 06ffff8081021850 by task init/1 [ 14.242004][ T1] The buggy address belongs to the object at ffffff8081021850 [ 14.242004][ T1] which belongs to the cache kmalloc-8 of size 8 [ 14.255669][ T1] The buggy address is located 0 bytes inside of [ 14.255669][ T1] 8-byte region [ffffff8081021850, ffffff8081021858)
A vulnerability in the Linux kernel's regmap-IRQ handling can lead to out-of-bounds memory access. This issue arises in the 'regmap_add_irq_chip_fwnode()' function, where the allocation of a 2D array for IRQ type registers is incorrectly managed. The function is supposed to allocate a matrix with a number of rows equal to 'num_config_bases' and columns equal to 'num_config_regs'. However, the current logic mistakenly allocates memory for 'num_config_regs' rows instead. This flaw can cause memory corruption, particularly when 'num_config_regs' exceeds 'num_config_bases'. The issue was reported by Amit Pundir, who experienced a crash on his Dragonboard 845c device due to this memory corruption.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. The specific commit that addresses this issue is '963b54df82b6d6206d7def273390bf3f7af558e1', which is included in the Linux kernel stable tree.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 8, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/6e7b2337ecd028bd888a1a0be4115b8a88faf838 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/963b54df82b6d6206d7def273390bf3f7af558e1 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/b1a726ad33e585e3d9fa70712df31ae105e4532c | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 8, 2025 | New CVE Received | kernel.org |
Volerion