[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2025-71139":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-15T22:50:23.791Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-CVE-2025-71139","In the Linux kernel, the following vulnerability has been resolved:  kernel/kexec: fix IMA when allocation happens in CMA area  *** Bug description ***  When I tested kexec with the latest kernel, I ran into the following warning:  [   40.712410] ------------[ cut here ]------------ [   40.712576] WARNING: CPU: 2 PID: 1562 at kernel/kexec_core.c:1001 kimage_map_segment+0x144/0x198 [...] [   40.816047] Call trace: [   40.818498]  kimage_map_segment+0x144/0x198 (P) [   40.823221]  ima_kexec_post_load+0x58/0xc0 [   40.827246]  __do_sys_kexec_file_load+0x29c/0x368 [...] [   40.855423] ---[ end trace 0000000000000000 ]---  *** How to reproduce ***  This bug is only triggered when the kexec target address is allocated in the CMA area. If no CMA area is reserved in the kernel, use the \"cma=\" option in the kernel command line to reserve one.  *** Root cause *** The commit 07d24902977e (\"kexec: enable CMA based contiguous allocation\") allocates the kexec target address directly on the CMA area to avoid copying during the jump. In this case, there is no IND_SOURCE for the kexec segment.  But the current implementation of kimage_map_segment() assumes that IND_SOURCE pages exist and map them into a contiguous virtual address by vmap().  *** Solution *** If IMA segment is allocated in the CMA area, use its page_address() directly.",null,[],[],[],[14],{"_key":15},"CVE-2025-71139",[],[],[],"2026-01-14T15:16:03.693Z","2026-06-15T19:06:00.839652807Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2025-71139",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,4.6,[40],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9},"lt6_18_5_1",true,"ecosystem","6.18.5-1","excluding"]