{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2023-53768","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-12-08T01:18:04.281Z","datePublished":"2025-12-08T01:19:31.353Z","dateUpdated":"2026-08-05T09:15:55.388Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T09:15:55.388Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nregmap-irq: Fix out-of-bounds access when allocating config buffers\n\nWhen allocating the 2D array for handling IRQ type registers in\nregmap_add_irq_chip_fwnode(), the intent is to allocate a matrix\nwith num_config_bases rows and num_config_regs columns.\n\nThis is currently handled by allocating a buffer to hold a pointer for\neach row (i.e. num_config_bases). After that, the logic attempts to\nallocate the memory required to hold the register configuration for\neach row. However, instead of doing this allocation for each row\n(i.e. num_config_bases allocations), the logic erroneously does this\nallocation num_config_regs number of times.\n\nThis scenario can lead to out-of-bounds accesses when num_config_regs\nis greater than num_config_bases. Fix this by updating the terminating\ncondition of the loop that allocates the memory for holding the register\nconfiguration to allocate memory only for each row in the matrix.\n\nAmit Pundir reported a crash that was occurring on his db845c device\ndue to memory corruption (see \"Closes\" tag for Amit's report). The KASAN\nreport below helped narrow it down to this issue:\n\n[   14.033877][    T1] ==================================================================\n[   14.042507][    T1] BUG: KASAN: invalid-access in regmap_add_irq_chip_fwnode+0x594/0x1364\n[   14.050796][    T1] Write of size 8 at addr 06ffff8081021850 by task init/1\n\n[   14.242004][    T1] The buggy address belongs to the object at ffffff8081021850\n[   14.242004][    T1]  which belongs to the cache kmalloc-8 of size 8\n[   14.255669][    T1] The buggy address is located 0 bytes inside of\n[   14.255669][    T1]  8-byte region [ffffff8081021850, ffffff8081021858)"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The overflow occurs in the regmap-irq chip registration path executed during local device driver probe/module load (wcd934x codec, pm8008 PMIC); there is no remote or network-facing input involved, so the attack surface is confined to the local system.\nAC:L - The out-of-bounds write is fully deterministic — `num_config_regs` (4) exceeds `num_config_bases` (1 for wcd934x) as compile-time constants, so every probe of the affected chip overflows the 8-byte allocation with no race, timing, or layout precondition.\nPR:L - No privilege check gates the vulnerable code — it runs unconditionally when the affected driver binds (at boot or on module load), so the corrupted heap state exists for any local user; the minimum meaningful local presence is an unprivileged account.\nUI:N - Driver probe happens automatically during boot or deferred probe with no victim action required; no user must open a file, mount, or attach a device.\nS:U - The corruption stays within the kernel's own slab allocator and security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - Three adjacent live `kmalloc-8` slab objects are overwritten with valid kernel heap pointers, planting kernel addresses into unrelated structures whose contents may subsequently be exposed, which defeats KASLR/heap-layout secrecy and constitutes memory corruption leverageable for disclosure.\nI:H - This is a heap out-of-bounds write that silently corrupts 24 bytes of neighboring in-use slab objects with pointer values; per kernel scoring practice an OOB write that clobbers adjacent live allocations is a High integrity impact.\nA:H - The corruption was reported and reproduced as a kernel crash on db845c hardware (KASAN invalid-access, followed by memory-corruption failures), so the flaw reliably renders the affected system unusable."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/base/regmap/regmap-irq.c"],"versions":[{"version":"faa87ce9196dbb074d75bd4aecb8bacf18f19b4e","lessThan":"b1a726ad33e585e3d9fa70712df31ae105e4532c","status":"affected","versionType":"git"},{"version":"faa87ce9196dbb074d75bd4aecb8bacf18f19b4e","lessThan":"6e7b2337ecd028bd888a1a0be4115b8a88faf838","status":"affected","versionType":"git"},{"version":"faa87ce9196dbb074d75bd4aecb8bacf18f19b4e","lessThan":"963b54df82b6d6206d7def273390bf3f7af558e1","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/base/regmap/regmap-irq.c"],"versions":[{"version":"6.0","status":"affected"},{"version":"0","lessThan":"6.0","status":"unaffected","versionType":"semver"},{"version":"6.1.40","lessThanOrEqual":"6.1.*","status":"unaffected","versionType":"semver"},{"version":"6.4.5","lessThanOrEqual":"6.4.*","status":"unaffected","versionType":"semver"},{"version":"6.5","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.1.40"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.4.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.5"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/b1a726ad33e585e3d9fa70712df31ae105e4532c"},{"url":"https://git.kernel.org/stable/c/6e7b2337ecd028bd888a1a0be4115b8a88faf838"},{"url":"https://git.kernel.org/stable/c/963b54df82b6d6206d7def273390bf3f7af558e1"}],"title":"regmap-irq: Fix out-of-bounds access when allocating config buffers","x_generator":{"engine":"bippy-1.2.0"}}}}