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

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-64502— iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices

CVSS 7.8 · High EPSS 0.15% · P5

Possible ATT&CK Techniques 1AI

T1205.002 · Socket Filters

Affected Version Matrix 8

VendorProductVersion RangeStatus
LinuxLinux132d44dc6966c1cf841ffe0f6f048165687e870b< 3394e0b3328422431cadaf314fa58d3717ed4936affected
132d44dc6966c1cf841ffe0f6f048165687e870b< 3bceb26dfaf7ba805b459e41c1d0ba916862dadeaffected
132d44dc6966c1cf841ffe0f6f048165687e870b< 91bc6767a4f55dc470d8a56b55b9f2ea09094efeaffected
6.14affected
< 6.14unaffected
6.18.39≤ 6.18.*unaffected
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-64502

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: adc: ad_sigma_delta: fix clear_pending_event for registerless devices
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices ad_sigma_delta_clear_pending_event() falls through to the status register read path for devices with has_registers = false and no rdy_gpiod. For such devices, ad_sd_read_reg() skips the address byte entirely and clocks raw MISO bytes with no address phase — making it byte-for-byte identical to reading conversion data. If a pending conversion result is present, this partially consumes it and corrupts the data stream for the subsequent ad_sd_read_reg() call in ad_sigma_delta_single_conversion(). Furthermore, with num_resetclks = 0 on these devices, data_read_len evaluates to 0. If the clocked byte has bit 7 clear, pending_event is set and the code attempts memset(data + 2, 0xff, 0 - 1), overflowing to SIZE_MAX and corrupting the heap. Fix by returning 0 immediately when neither rdy_gpiod nor has_registers is set. This is safe for all current registerless devices: ad7191 and ad7780 (with powerdown GPIO) are reset between conversions by CS deassertion, so there is no stale result to drain; ad7780 (without powerdown GPIO) and max11205 are continuously-converting and cycle ~DRDY at the output data rate regardless of whether the previous result was read, so the next falling edge fires naturally. A future registerless device that holds ~DRDY asserted until data is read would be broken by this early return and would require either num_resetclks set or a rdy-gpio. The same heap corruption is reachable on any device with rdy_gpiod set but num_resetclks = 0: if the GPIO indicates a pending event, the drain path executes memset(data + 2, 0xff, 0 - 1) regardless of has_registers. Add an explicit data_read_len == 0 guard after the pending event check; the stale result is then consumed by the first ad_sd_read_reg() call in ad_sigma_delta_single_conversion().
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 132d44dc6966c1cf841ffe0f6f048165687e870b ~ 3394e0b3328422431cadaf314fa58d3717ed4936 -
LinuxLinux 6.14 -

II. Public POCs for CVE-2026-64502

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-64502

登录查看更多情报信息。

Patches & Fixes for CVE-2026-64502 (3)

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

CVE-2026-643979.8 CRITICALksmbd: serialize QUERY_DIRECTORY requests per file
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-643919.8 CRITICALksmbd: use opener credentials for ADS I/O
CVE-2026-643999.8 CRITICALksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE
CVE-2026-645239.8 CRITICALnet/handshake: Take a long-lived file reference at submit
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-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-644109.8 CRITICALnetfilter: flowtable: IPIP tunnel hardware offload is not yet support
CVE-2026-643929.1 CRITICALksmbd: use opener credentials for delete-on-close
CVE-2026-644509.1 CRITICALtipc: fix out-of-bounds read in broadcast Gap ACK blocks
CVE-2026-642699.1 CRITICALRDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg
CVE-2026-643199.1 CRITICALnvmet-auth: validate reply message payload bounds against transfer length
CVE-2026-643939.1 CRITICALksmbd: run set info with opener credentials

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

IV. Related Vulnerabilities

V. Comments for CVE-2026-64502

No comments yet


Leave a comment