** Description changed: Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of active io-memory ranges. This could impact kernel debugability. In that case, you may reboot with iomem=relaxed on the kernel command line to override this setting. This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in many other major distro kernels[2]. [1] https://kspp.github.io/Recommended_Settings [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ - In Ubuntu impish: + In Ubuntu: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* - /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set - /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set - /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set - /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set + /boot/config-6.14.0-13-generic:# CONFIG_IO_STRICT_DEVMEM is not set + /boot/config-6.14.0-15-generic:# CONFIG_IO_STRICT_DEVMEM is not set - In Debian 11: + In Debian 12: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* - /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y - /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y + /boot/config-6.1.0-31-amd64:CONFIG_IO_STRICT_DEVMEM=y + /boot/config-6.1.0-32-amd64:CONFIG_IO_STRICT_DEVMEM=y - In Debian sid: + In Debian sid+experimental: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* - /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y - /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y + /boot/config-6.12.21-amd64:CONFIG_IO_STRICT_DEVMEM=y + /boot/config-6.13-amd64:CONFIG_IO_STRICT_DEVMEM=y
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959384 Title: CONFIG_IO_STRICT_DEVMEM could be enabled Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of active io-memory ranges. This could impact kernel debugability. In that case, you may reboot with iomem=relaxed on the kernel command line to override this setting. This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in many other major distro kernels[2]. [1] https://kspp.github.io/Recommended_Settings [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ In Ubuntu: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* /boot/config-6.14.0-13-generic:# CONFIG_IO_STRICT_DEVMEM is not set /boot/config-6.14.0-15-generic:# CONFIG_IO_STRICT_DEVMEM is not set In Debian 12: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* /boot/config-6.1.0-31-amd64:CONFIG_IO_STRICT_DEVMEM=y /boot/config-6.1.0-32-amd64:CONFIG_IO_STRICT_DEVMEM=y In Debian sid+experimental: $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-* /boot/config-6.12.21-amd64:CONFIG_IO_STRICT_DEVMEM=y /boot/config-6.13-amd64:CONFIG_IO_STRICT_DEVMEM=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
