Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-64498— iio: buffer: hw-consumer: free scan_mask on buffer release

AI Predicted 4.4 Difficulty: Moderate EPSS 0.15% · P5

Affected Version Matrix 6

VendorProductVersion RangeStatus
LinuxLinux9a2e1233d38c460ad07f36901931f3674a32d1ed< fb8e18f8ca724bd4de4643cad5b7c7230b9a5a71affected
9a2e1233d38c460ad07f36901931f3674a32d1ed< 6325d6e2204327965b849c0a16efb6ac9202e5a8affected
7.1affected
< 7.1unaffected
7.1.4≤ 7.1.*unaffected
7.2-rc1≤ *unaffected
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-64498

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
iio: buffer: hw-consumer: free scan_mask on buffer release
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: iio: buffer: hw-consumer: free scan_mask on buffer release The scan_mask lifetime changed in commit 9a2e1233d38c ("iio: buffer: hw-consumer: remove redundant scan_mask flexible array"). Before that change, the scan mask storage was embedded in struct hw_consumer_buffer, so iio_hw_buf_release() could free the whole allocation with a single kfree(hw_buf). That commit moved the scan mask to a separate bitmap_zalloc() allocation stored in buffer.scan_mask, but left iio_hw_buf_release() unchanged. Free the scan mask in iio_hw_buf_release() before freeing the buffer wrapper.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 9a2e1233d38c460ad07f36901931f3674a32d1ed ~ fb8e18f8ca724bd4de4643cad5b7c7230b9a5a71 -
LinuxLinux 7.1 -

II. Public POCs for CVE-2026-64498

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-64498

登录查看更多情报信息。

Patches & Fixes for CVE-2026-64498 (2)

Same Patch Batch · Linux · 2026-07-25 · 274 CVEs total

CVE-2026-643919.8 CRITICALksmbd: use opener credentials for ADS I/O
CVE-2026-642689.8 CRITICALRDMA/siw: bound Read Response placement to the RREAD length
CVE-2026-643849.8 CRITICALsmb: client: fix change notify replay double-free
CVE-2026-643839.8 CRITICALsmb: client: fix double-free in SMB2_flush() replay
CVE-2026-643859.8 CRITICALsmb: client: fix double-free in SMB2_ioctl() replay
CVE-2026-643869.8 CRITICALsmb: client: fix query_info() replay double-free
CVE-2026-643879.8 CRITICALsmb: client: fix query directory replay double-free
CVE-2026-644399.8 CRITICALcrypto: krb5 - filter out async aead implementations at alloc
CVE-2026-643039.8 CRITICALspi: fsl-lpspi: terminate the RX channel on TX prepare failure path
CVE-2026-643559.8 CRITICALbpf: Reject fragmented frames in devmap
CVE-2026-644599.8 CRITICALtcp: restore RCU grace period in tcp_ao_destroy_sock
CVE-2026-643999.8 CRITICALksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE
CVE-2026-644109.8 CRITICALnetfilter: flowtable: IPIP tunnel hardware offload is not yet support
CVE-2026-643979.8 CRITICALksmbd: serialize QUERY_DIRECTORY requests per file
CVE-2026-645239.8 CRITICALnet/handshake: Take a long-lived file reference at submit
CVE-2026-643209.1 CRITICALnvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page
CVE-2026-643929.1 CRITICALksmbd: use opener credentials for delete-on-close
CVE-2026-642699.1 CRITICALRDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg
CVE-2026-643939.1 CRITICALksmbd: run set info with opener credentials
CVE-2026-643199.1 CRITICALnvmet-auth: validate reply message payload bounds against transfer length

Showing top 20 of 274 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-64498

No comments yet


Leave a comment