[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cve-CVE-2026-98032":3},{"id":4,"cve_id":5,"euvd_id":6,"summary":7,"published":8,"cvss_data":9,"is_remote":10,"cwes":11,"cpes":12,"technologies":13,"references":14,"score":18,"epss_score":19,"epss_percentile":20,"is_kev":10,"cisa_kev_date_added":21,"cisa_kev_due_date":21,"cisa_ssvc":22,"attack_mappings":28,"exploits":29},395942,"CVE-2026-98032","EUVD-2026-86685","In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix subbuf resize races with trace_pipe_raw readers\n\nConcurrent subbuffer resizes may crash trace_pipe_raw readers or leak\nuninitialized memory to userspace due to stale size values.\n\nModify ring_buffer_alloc_read_page() to handle the resizing of an\nexisting buffer_data_read_page if necessary and add a new\nring_buffer_read_page_size(). This new function enables ring-buffer\nbuffer_data_read_page users to not call the racy\nring_buffer_subbuf_size_get(). This makes the spare_size member of\nftrace_buffer_info redundant.\n\nFinally, handle buffer_data_read_page\u002Freader_page order discrepancy in\nring_buffer_read_page(). On a mismatch simply copy manually the data to\nthe buffer_data_read_page.","2026-09-25T11:17:00Z",{},false,[],[],[],[15,16,17],"https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002F75b37b8369778b69ce9738d1c97685a1615cb252","https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002Fdae8dda341d2d9034a90d59e8a7d502e1263813f","https:\u002F\u002Fgit.kernel.org\u002Fstable\u002Fc\u002F3f30b2cd4eba45c05f822f03f1b0f4077d6d4dc3",0,0.00168,0.05987,null,{"timestamp":21,"automatable":23,"tech_impact":24,"exploitation":25,"cisa_decision":26,"cisa_remediation_timeline":27},"no","partial","none",{},"FSU",[],[]]