OESA-2025-2409

Source
https://www.openeuler.org/en/security/security-bulletins/detail/?id=openEuler-SA-2025-2409
Import Source
https://repo.openeuler.org/security/data/osv/OESA-2025-2409.json
JSON Data
https://api.osv.dev/v1/vulns/OESA-2025-2409
Upstream
Published
2025-10-11T11:09:29Z
Modified
2026-08-18T01:19:13Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
kernel security update
Details

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking

If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen:

BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, ... preempt_count: 1, expected: 0 ... Call Trace: ... __might_resched+0x104/0x10e __might_sleep+0x3e/0x62 mutex_lock+0x20/0x4c regmap_lock_mutex+0x10/0x18 regmap_update_bits_base+0x2c/0x66 mcp23s08_irq_set_type+0x1ae/0x1d6 __irq_set_trigger+0x56/0x172 __setup_irq+0x1e6/0x646 request_threaded_irq+0xb6/0x160 ...

We observed the problem while experimenting with a touchscreen driver which used MCP23017 IO expander (I2C).

The regmap in the pinctrl-mcp23s08 driver uses a mutex for protection from concurrent accesses, which is the default for regmaps without .fast_io, .disable_locking, etc.

mcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter locks the mutex.

However, __setup_irq() locks desc->lock spinlock before calling these functions. As a result, the system tries to lock the mutex whole holding the spinlock.

It seems, the internal regmap locks are not needed in this driver at all. mcp->lock seems to protect the regmap from concurrent accesses already, except, probably, in mcp_pinconf_get/set.

mcp23s08_irq_set_type() and mcp23s08_irq_mask/unmask() are called under chip_bus_lock(), which calls mcp23s08_irq_bus_lock(). The latter takes mcp->lock and enables regmap caching, so that the potentially slow I2C accesses are deferred until chip_bus_unlock().

The accesses to the regmap from mcp23s08_probe_one() do not need additional locking.

In all remaining places where the regmap is accessed, except mcp_pinconf_get/set(), the driver already takes mcp->lock.

This patch adds locking in mcp_pinconf_get/set() and disables internal locking in the regmap config. Among other things, it fixes the sleeping in atomic context described above.(CVE-2024-57889)

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

mm/smaps: fix race between smaps_hugetlb_range and migration

smaps_hugetlb_range() handles the pte without holdling ptl, and may be concurrenct with migration, leaing to BUG_ON in pfn_swap_entry_to_page(). The race is as follows.

smaps_hugetlb_range migrate_pages huge_ptep_get remove_migration_ptes folio_unlock pfn_swap_entry_folio BUG_ON

To fix it, hold ptl lock in smaps_hugetlb_range().(CVE-2025-39754)

Database specific
{
    "severity": "Medium"
}
References

Affected packages

openEuler:24.03-LTS / kernel

Package

Name
kernel
Purl
pkg:rpm/openEuler/kernel&distro=openEuler-24.03-LTS

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
6.6.0-111.0.0.103.oe2403

Ecosystem specific

{
    "aarch64": [
        "bpftool-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "bpftool-debuginfo-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-debuginfo-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-debugsource-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-devel-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-headers-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-source-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-tools-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-tools-debuginfo-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "kernel-tools-devel-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "perf-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "perf-debuginfo-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "python3-perf-6.6.0-111.0.0.103.oe2403.aarch64.rpm",
        "python3-perf-debuginfo-6.6.0-111.0.0.103.oe2403.aarch64.rpm"
    ],
    "src": [
        "kernel-6.6.0-111.0.0.103.oe2403.src.rpm"
    ],
    "x86_64": [
        "bpftool-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "bpftool-debuginfo-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-debuginfo-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-debugsource-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-devel-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-headers-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-source-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-tools-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-tools-debuginfo-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "kernel-tools-devel-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "perf-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "perf-debuginfo-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "python3-perf-6.6.0-111.0.0.103.oe2403.x86_64.rpm",
        "python3-perf-debuginfo-6.6.0-111.0.0.103.oe2403.x86_64.rpm"
    ]
}

Database specific

source
"https://repo.openeuler.org/security/data/osv/OESA-2025-2409.json"