Changes in Kconfig

637315cb400eed1dbe721954fea437a61a2d65b2 - Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEAD

Tue, 18 Aug 2026 13:07:31 +0200

Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEADKVM/riscv changes for 7.3- Svadu/Zicfiss/Zicfilp FWFT support for Guest- Use try_cmpxchg for IMSIC MRIF RMW- More arch-specific tracepoints in KVM RISC-V- Eager Page Splitting for KVM RISC-V- Optimize hfence request handling for SMP Guests- Improve dirty log clearing by skipping zero bits in mask- Guard HFENCE range loops against overflow- CPU PM notifiers in KVM RISC-V for non-retentive idle states- Fix kernel-mode vector context save/restore for Guest List of files: /linux/security/integrity/ima/Kconfig

efe86f088f48f18c27b648e5724048947f3b7fb4 - Merge drm/drm-next into drm-xe-next

Tue, 14 Jul 2026 15:40:31 +0200

Merge drm/drm-next into drm-xe-nextSync some i915/display changesSigned-off-by: Rodrigo Vivi List of files: /linux/security/integrity/ima/Kconfig

6d177908bad5992e17669030db41caab88041d5e - Merge drm/drm-next into drm-intel-next

Tue, 30 Jun 2026 14:55:43 +0200

Merge drm/drm-next into drm-intel-nextSync with v7.2-rc1.Signed-off-by: Jani Nikula List of files: /linux/security/integrity/ima/Kconfig

827b9aabd3ea3e96d5e48abed9f44dbd1e550d4e - Merge drm/drm-next into drm-misc-next

Tue, 30 Jun 2026 10:16:00 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to get drm-misc-next to v7.2-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/security/integrity/ima/Kconfig

7dd19adaaac9a161723a24de7c270861063ec6ac - Merge tag 'v7.2-rc1' into drm-rust-next

Sun, 28 Jun 2026 22:39:43 +0200

Merge tag 'v7.2-rc1' into drm-rust-nextMerge v7.2-rc1 into drm-rust-next to start the next cycle.Devres now requires T: 'static, which conflicts with shmem::Object usingDevres> without that bound. Resolve by adding 'staticas a supertrait to DriverObject and DeviceContext, which does notrestrict any current use cases since DriverObject is always implementedon owned, refcounted types and DeviceContext is a sealed marker traitwith only unit-type implementors.If DriverObject (or DeviceContext) ever becomes lifetime-parameterized(e.g. via a GAT for TTM backed objects), the 'static supertrait can berelaxed at that point.Signed-off-by: Danilo Krummrich List of files: /linux/security/integrity/ima/Kconfig

a51ec5e8e5dae80824239f0344210060cb92a4b0 - Merge tag 'integrity-v7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity

Thu, 20 Aug 2026 02:17:17 +0200

Merge tag 'integrity-v7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrityPull integrity updates from Mimi Zohar: - TPM initialization is sometimes delayed until deferred_probe_initcall Since ordering is not guaranteed within the same initcall level, IMA may initialize before the TPM and fall back to TPM-bypass mode. A new config option, CONFIG_IMA_INIT_LATE_SYNC, allows those building the kernel to defer IMA initialization to late_initcall_sync, accepting the integrity risk of missing early measurements in exchange for avoiding TPM-bypass mode. - The raw policy rules are now measured, as well as the complete policy, closing a gap in integrity measurement coverage* tag 'integrity-v7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity: ima: measure userspace policy writes before parsing ima: add critical data measurement for loaded policy security: ima: rename boot_aggregate when ima is initialised at late_sync security: ima: introduce IMA_INIT_LATE_SYNC option security: lsm: allow LSMs to register for late_initcall_sync init List of files: /linux/security/integrity/ima/Kconfig

3d5e48944e824bddc20d7b874e784f7b279636fe - Merge branch 'for-7.3/steam' into for-linus

Wed, 19 Aug 2026 09:16:28 +0200

Merge branch 'for-7.3/steam' into for-linus- initial support for 2026 Steam Controller (Vicki Pfau)- support for sensor events on the 2025 Steam Controller (Vicki Pfau)- assorted fixes, improvements and code refactoring (Vicki Pfau) List of files: /linux/security/integrity/ima/Kconfig

0eaed89c18aeedf0898baf2dbf5ff027c6795152 - Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource

Mon, 17 Aug 2026 10:29:52 +0200

Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource - Use designated initializers for sh_mtu2, sh_cmt, and sh_tmu, and drop the unused initializer in the platform_device_id table for sh_mtu2 (Uwe Kleine-König) - Remove redundant dev_err()/dev_err_probe() messages when devm_request_*_irq() fails, as the helper already logs an error message (Pan Chuang) - Fix a boot hang on Allwinner D1 when a forced minimum delta is used with the sun4i timer (Felix Yan) - Fix an IRQ leak in the cpuhp_setup_state() error path by freeing the IRQ on failure in the NXP PIT driver (WenTao Liang) - Fix incorrect unmapping of shared MMIO between the clocksource and clockevent drivers. If one of them fails to initialize, the error path unmaps the shared MMIO region, leaving the other driver with an invalid mapping on clps711x (Guangshuo Li) - Make the samsung_pwm driver compatible with PREEMPT_RT by replacing regular spinlocks with raw_spinlock_t in atomic contexts (Marek Szyprowski) - Use __raw_readl() and __raw_writel() instead of ioread32() and iowrite32() to support SWAP_IO_SPACE in the rtl-otto driver (Rustam Adilov) - Fix a missing clk_disable_unprepare() call in the timer initialization error path of the Armada driver (Yuho Choi)Link: https://lore.kernel.org/lkml/75feea31-683d-45a1-87f4-ab045e0152ae@oss.qualcomm.com List of files: /linux/security/integrity/ima/Kconfig

b4d85f863e5a6f1fa01b186001af0f68f4f5239e - Merge branch 'next' into for-linus

Sat, 15 Aug 2026 06:26:07 +0200

Merge branch 'next' into for-linusPrepare input updates for 7.3 merge window. List of files: /linux/security/integrity/ima/Kconfig

1ebe7997b53b7ff956a089593723d8cb6faffdd6 - security: ima: introduce IMA_INIT_LATE_SYNC option

Fri, 05 Jun 2026 16:43:23 +0200

security: ima: introduce IMA_INIT_LATE_SYNC optionTo generate the boot_aggregate log in the IMA subsystem withTPM PCR values, the TPM driver must be built as built-in andmust be probed before the IMA subsystem is initialized.However, when the TPM device operates over the FF-A protocol usingthe CRB interface, probing fails and returns -EPROBE_DEFER ifthe tpm_crb_ffa device — an FF-A device that provides the communicationinterface to the tpm_crb driver — has not yet been probed.To ensure the TPM device operating over the FF-A protocol withthe CRB interface is probed before IMA initialization,the following conditions must be met:1. The corresponding ffa_device must be registered, which is done via ffa_init().2. The tpm_crb_driver must successfully probe this device via tpm_crb_ffa_init().3. The tpm_crb driver using CRB over FF-A can then be probed successfully. (See crb_acpi_add() and tpm_crb_ffa_init() for reference.)Unfortunately, ffa_init(), tpm_crb_ffa_init(), and crb_acpi_driver_init()are all registered with device_initcall, which meanscrb_acpi_driver_init() may be invoked before ffa_init() andtpm_crb_ffa_init() are completed.When this occurs, probing the TPM device is deferred.However, the deferred probe can happen after the IMA subsystemhas already been initialized, since IMA initialization is performedduring late_initcall, and deferred_probe_initcall() is performedat the same level.And the similar situation is reported on TPM devices attached on SPIbus[0].To resolve this, introduce IMA_INIT_LATE_SYNC option to initialiseIMA at late_inicall_sync so that IMA is initialized with the TPMdevice probed deferred.When this option is enabled, modules that access files in theinitramfs through usermode helper calls such as request_module()during initcall must not be built-in. Otherwise, IMA may missmeasuring those files [1].Link: https://lore.kernel.org/all/aYXEepLhUouN5f99@earth.li/ [0]Link: https://lore.kernel.org/all/2b3782398cc17ce9d355490a0c42ebce9120a9ae.camel@linux.ibm.com/ [1]Suggested-by: Mimi Zohar Signed-off-by: Yeoreum Yun [zohar@linux.ibm.com: Fixed Kconfig merge conflict]Signed-off-by: Mimi Zohar List of files: /linux/security/integrity/ima/Kconfig

76904fccf81936c084faebc73ac72c0919a42941 - Merge tag 'v7.2-rc3' into next

Tue, 14 Jul 2026 04:06:00 +0200

Merge tag 'v7.2-rc3' into nextSync up with mainline to pull in stable fixes to avoid merge conflicts. List of files: /linux/security/integrity/ima/Kconfig

00599d4841790d05401820a96cf7edb193888b00 - Merge drm/drm-fixes into drm-misc-fixes

Mon, 29 Jun 2026 17:58:00 +0200

Merge drm/drm-fixes into drm-misc-fixesPull in tag v7.2-rc1 so that drm-misc-fixes becomes useful again,and drm-misc-next-fixes can be closed.Signed-off-by: Maarten Lankhorst List of files: /linux/security/integrity/ima/Kconfig

7a0e692a0381254b2f77c54dec100cd3325a6fdf - Merge branch 'next' into for-linus

Tue, 23 Jun 2026 08:10:08 +0200

Merge branch 'next' into for-linusPrepare input updates for 7.2 merge window. List of files: /linux/security/integrity/ima/Kconfig

0798268aa4c26ece25020b3ddeeef9a5941209c0 - Merge tag 'integrity-v7.2' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity

Fri, 19 Jun 2026 20:32:05 +0200

Merge tag 'integrity-v7.2' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrityPull IMA updates from Mimi Zohar: - Introduce IMA and EVM post-quantum ML-DSA signature support ML-DSA signature support for IMA and EVM is limited to sigv3 signatures, which calculates and verifies a hash of a compact structure containing the file data/metadata hash, hash type, and hash algorithm. IMA and EVM still calculate the file data/metadata hashes respectively. - Introduce support for removing IMA measurement list records stored in kernel memory The IMA measurement list can grow large depending on policy, but removing records breaks remote attestation, unless they are safely preserved and made available for attestation requests. Until environments are prepared to preserve the measurement records, a new CONFIG_IMA_STAGING Kconfig option is introduced to guard against deletion. Several approaches for removing measurement list records were evaluated but rejected due to filesystem constraints, the introduction of a new critical data record, and locking concerns. Two methods are being upstreamed: staged deletion with confirmation, and staged deletion of N records without confirmation. Both methods minimize the period during which new measurements are blocked from being appended to the measurement list by staging the measurement list. A comparison of the two methods is included in the documentation. - Some code cleanup, and a couple of bug fixes* tag 'integrity-v7.2' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity: doc: security: Add documentation of exporting and deleting IMA measurements ima: Support staging and deleting N measurements records ima: Add support for flushing the hash table when staging measurements ima: Add support for staging measurements with prompt ima: Introduce ima_dump_measurement() ima: Use snprintf() in create_securityfs_measurement_lists ima: Mediate open/release method of the measurements list ima: Introduce _ima_measurements_start() and _ima_measurements_next() ima: Introduce per binary measurements list type binary_runtime_size value ima: Introduce per binary measurements list type ima_num_records counter ima: Replace static htable queue with dynamically allocated array ima: Remove ima_h_table structure evm: terminate and bound the evm_xattrs read buffer integrity: Add support for sigv3 verification using ML-DSA keys integrity: Refactor asymmetric_verify for reusability integrity: Check that algo parameter is within valid range integrity: Check for NULL returned by asymmetric_key_public_key ima: return error early if file xattr cannot be changed ima: Fix sigv3 signature handling for EVM_IMA_XATTR_DIGSIG List of files: /linux/security/integrity/ima/Kconfig

fcb0318a29696c13c9f8af0109855793a34371e6 - ima: Support staging and deleting N measurements records

Fri, 05 Jun 2026 19:22:35 +0200

ima: Support staging and deleting N measurements recordsAdd support for sending a value N between 1 and ULONG_MAX to the IMAoriginal measurement interface. This value represents the number ofmeasurements that should be deleted from the current measurements list. Inthis case, measurements are staged in an internal non-user visible list,and immediately deleted.This staging method allows the remote attestation agents to easily separatethe measurements that were verified (staged and deleted) from those thatweren't due to the race between taking a TPM quote and reading themeasurements list.In order to minimize the locking time of ima_extend_list_mutex, deletingN records is realized by doing a lockless walk in the current measurementslist to determine the N-th entry to cut, to cut the current measurementslist under the lock, and by deleting the excess records after releasing thelock.Flushing the hash table is not supported for N records, since it wouldrequire removing the N records one by one from the hash table under theima_extend_list_mutex lock, which would increase the locking time.Link: https://github.com/linux-integrity/linux/issues/1Co-developed-by: Steven Chen Signed-off-by: Steven Chen Signed-off-by: Roberto Sassu Signed-off-by: Mimi Zohar List of files: /linux/security/integrity/ima/Kconfig

e9b491e27bf6b9401e2e521955787a7a6e2bf808 - ima: Add support for staging measurements with prompt

Fri, 05 Jun 2026 19:22:33 +0200

ima: Add support for staging measurements with promptIntroduce the ability of staging the IMA measurement list and deleting themwith a prompt.Staging means moving the current measurement list records to a separatelocation, and allowing users to read and delete it. This causes the currentmeasurement list to be emptied (since records were moved) and newmeasurements to be added on the empty list. Staging can be done only onceat a time. In the event of kexec(), staging is aborted and staged recordswill be carried over to the new kernel.Introduce ascii_runtime_measurements__staged andbinary_runtime_measurements__staged interfaces to access and deletethe measurements.Use 'echo A > ' and'echo D > ' to respectively stage and delete theentire measurements list. Locking of these interfaces is also mediated witha call to _ima_measurements_open() and with ima_measurements_release().Implement the staging functionality by introducing the new globalmeasurements list ima_measurements_staged, and ima_queue_stage() andima_queue_staged_delete_all() to respectively move measurements from thecurrent measurements list to the staged one, and to move stagedmeasurements to the ima_measurements_trim list for deletion. Introduceima_queue_delete() to delete the measurements.Staging is forbidden after measurement is suspended, and between stagingand deleting, so that walking the staged and current measurements list canbe done locklessly in ima_dump_measurement_list(). Strict ordering ofsuspending and dumping is enforced by two reboot notifiers with differentpriority. Refusing to delete staged measurements also signals to user spacethat those measurements are already carried over to the secondary kernel,so that it does not save them twice.Finally, introduce the BINARY_STAGED and BINARY_FULL binary measurementslist types, to maintain the counters and the binary size of stagedmeasurements and the full measurements list (including records that werestaged). BINARY still represents the current binary measurements list.Use the binary size for the BINARY + BINARY_STAGED types inima_add_kexec_buffer(), since both measurements list types are copied tothe secondary kernel during kexec. Use BINARY_FULL inima_measure_kexec_event(), to generate a critical data record.It should be noted that the BINARY_FULL counter is not passed throughkexec. Thus, the number of records included in the kexec critical datarecords refers to the records since the critical data records generatedfrom the previous kexec event.Note: This code derives from the Alt-IMA Huawei project, whose license is GPL-2.0 OR MIT.Link: https://github.com/linux-integrity/linux/issues/1Suggested-by: Gregory Lumen (staging revert)Signed-off-by: Roberto Sassu Tested-by: Stefan Berger Signed-off-by: Mimi Zohar List of files: /linux/security/integrity/ima/Kconfig

fff88709f9a9153af85b5224b4594caa5387ca60 - Merge tag 'v7.1-rc6' into next

Mon, 01 Jun 2026 04:43:25 +0200

Merge tag 'v7.1-rc6' into nextSync up with mainline to pull in a fix to IMS PCU driver and otherenhancements. List of files: /linux/security/integrity/ima/Kconfig

5c8cbca290acdd49a694b36c0af76ba0c00bbf12 - Merge branch '20260507-ubwc-rework-v4-4-c19593d20c1d@oss.qualcomm.com' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into HEAD

Thu, 21 May 2026 22:36:50 +0200

Merge branch '20260507-ubwc-rework-v4-4-c19593d20c1d@oss.qualcomm.com' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into HEADMerge the branch with the soc/qcom changes, required for the next UBWCpatches.Signed-off-by: Dmitry Baryshkov List of files: /linux/security/integrity/ima/Kconfig

09d6818d3bdc1ea6e49a425040528cbdbc97bc0a - Merge branch 'linus' into timers/clocksource

Mon, 18 May 2026 11:01:07 +0200

Merge branch 'linus' into timers/clocksource... to bring it up to date for new changes. List of files: /linux/security/integrity/ima/Kconfig

658a6021492ad3b1b8a6e9a83963a1fad35a2af8 - Merge drm/drm-next into drm-intel-next

Fri, 15 May 2026 13:01:15 +0200

Merge drm/drm-next into drm-intel-nextSome Display Port Adaptive Sync depends on drm work.Signed-off-by: Rodrigo Vivi List of files: /linux/security/integrity/ima/Kconfig