{"schema_version":"1.7.2","id":"OESA-2025-2409","modified":"2025-10-11T13:21:16Z","published":"2025-10-11T13:21:16Z","upstream":["CVE-2024-57889","CVE-2025-39754"],"summary":"kernel security update","details":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking\n\nIf a device uses MCP23xxx IO expander to receive IRQs, the following\nbug can happen:\n\n  BUG: sleeping function called from invalid context\n    at kernel/locking/mutex.c:283\n  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, ...\n  preempt_count: 1, expected: 0\n  ...\n  Call Trace:\n  ...\n  __might_resched+0x104/0x10e\n  __might_sleep+0x3e/0x62\n  mutex_lock+0x20/0x4c\n  regmap_lock_mutex+0x10/0x18\n  regmap_update_bits_base+0x2c/0x66\n  mcp23s08_irq_set_type+0x1ae/0x1d6\n  __irq_set_trigger+0x56/0x172\n  __setup_irq+0x1e6/0x646\n  request_threaded_irq+0xb6/0x160\n  ...\n\nWe observed the problem while experimenting with a touchscreen driver which\nused MCP23017 IO expander (I2C).\n\nThe regmap in the pinctrl-mcp23s08 driver uses a mutex for protection from\nconcurrent accesses, which is the default for regmaps without .fast_io,\n.disable_locking, etc.\n\nmcp23s08_irq_set_type() calls regmap_update_bits_base(), and the latter\nlocks the mutex.\n\nHowever, __setup_irq() locks desc->lock spinlock before calling these\nfunctions. As a result, the system tries to lock the mutex whole holding\nthe spinlock.\n\nIt seems, the internal regmap locks are not needed in this driver at all.\nmcp->lock seems to protect the regmap from concurrent accesses already,\nexcept, probably, in mcp_pinconf_get/set.\n\nmcp23s08_irq_set_type() and mcp23s08_irq_mask/unmask() are called under\nchip_bus_lock(), which calls mcp23s08_irq_bus_lock(). The latter takes\nmcp->lock and enables regmap caching, so that the potentially slow I2C\naccesses are deferred until chip_bus_unlock().\n\nThe accesses to the regmap from mcp23s08_probe_one() do not need additional\nlocking.\n\nIn all remaining places where the regmap is accessed, except\nmcp_pinconf_get/set(), the driver already takes mcp->lock.\n\nThis patch adds locking in mcp_pinconf_get/set() and disables internal\nlocking in the regmap config. Among other things, it fixes the sleeping\nin atomic context described above.(CVE-2024-57889)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/smaps: fix race between smaps_hugetlb_range and migration\n\nsmaps_hugetlb_range() handles the pte without holdling ptl, and may be\nconcurrenct with migration, leaing to BUG_ON in pfn_swap_entry_to_page(). \nThe race is as follows.\n\nsmaps_hugetlb_range              migrate_pages\n  huge_ptep_get\n                                   remove_migration_ptes\n\t\t\t\t   folio_unlock\n  pfn_swap_entry_folio\n    BUG_ON\n\nTo fix it, hold ptl lock in smaps_hugetlb_range().(CVE-2025-39754)","affected":[{"package":{"ecosystem":"openEuler:24.03-LTS","name":"kernel","purl":"pkg:rpm/openEuler/kernel&distro=openEuler-24.03-LTS"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"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"]}}],"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2409"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57889"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39754"}],"database_specific":{"severity":"Medium"}}