CVE-2025-31208: Double Free
Published May 12, 2025
·Updated
afpfs. The issue was addressed with improved memory handling.
Other sources
afpfs. This issue was addressed with improved checks.
— Apple
AirDrop. A permissions issue was addressed with additional restrictions.
— Apple
Apple Intelligence Reports. A permissions issue was addressed with additional restrictions.
— Apple
AppleJPEG. The issue was addressed with improved input sanitization.
— Apple
Audio. A double free issue was addressed with improved memory management.
— Apple
Credit
Joseph Ravichandran@@0xjprx(MIT CSAIL), Dave G., Hossein Lotfi@@hosselot(Trend Micro Zero Day Initiative), Dillon Franke(Google Project Zero), wac(Trend Micro Zero Day Initiative), Csaba Fitzl@@theevilbit(Kandji), an anonymous researcher, Lyutoon(Atredis Partners), YenKoc(Atredis Partners), Dayton Pidhirney(Atredis Partners), Mateusz Krzywicki@@krzywix, Michael DePlante@@izobashi(Trend Micro Zero Day Initiative), Lucas Leong@@_wmliang_(Trend Micro Zero Day Initiative), Christian Kohlschütter, CVE-2024-8176, Paweł Płatek (Trail(Bits), LFY@@secsys(Fudan University), CVE-2025-26465, CVE-2025-26466, wac, Kirin@@Pwnrin, 7feilee, Eric Dorphy(Twin Cities App Dev LLC), Adam M., Lyutoon, YenKoc, Guilherme Rambo(Best Buddy Apps), Apple, Google Threat Analysis Group, Saagar Jha, Tony Iskow@@Tybbow, Google V8 Security Team, Andreas Jaegersberger & Ro Achterberg(Nosebeard Labs), rheza@@ginggilBesel(Palo Alto Networks), Edouard Bochin@@le_douds(Palo Alto Networks), Tao Yan@@Ga1ois(Palo Alto Networks), Nan Wang@@eternalsakura13, Ignacio Sanmillan@@ulexec, Jiming Wang, Jikai Ren, Yuhao Hu, Yan Kang, Chenggang Wu, Xiaojie Wei, Ivan Fratric(Google Project Zero), Juergen Schmied(Lynck GmbH), jioundai(360 Vulnerability Research Institute), chen fengjiao(HBC), Ron Masas(BREAKPOINT), Wang Yu(Cyberserval), Andrew James Gonzalez, Richard Hyunho Im@@richeeta, Andr.Ess, Noah Gregory (wts.dev), Thibaud Kehler, 秦若涵, 崔志伟, 崔宝江, Deval Jariwala, Dalibor Milanovic, YingQi Shi@@Mas0nShi(DBAppSecurity's WeBin lab), Duy Trần@@khanhduytran0, Shehab Khan, CertiK@@CertiK, Thomas Völkl@@vollkorntomate, SEEMOO, TU Darmstadt, Kirin@@Pwnrin(Fudan University), Bohdan Stasiuk@@bohdan_stasiuk, Sourabhkumar Mishra, @@RenwaX23, Ryan Dowd@@_rdowd
Affected Software
18 affected componentsFixes available
Apple macOS Sonoma<14.7.6
14.7.6
Apple macOS Sequoia<15.5
15.5
Apple tvOS<18.5
18.5
Apple visionOS<2.5
2.5
Apple iOS<18.5
18.5
Apple iPadOS<18.5
18.5
Apple WatchOS<11.5
11.5
Apple macOS Ventura<13.7.6
13.7.6
Apple iPadOS<17.7.7
17.7.7
Apple iPadOS<17.7.7
Apple iPadOS>=18.0<18.5
Apple iPhone OS<18.5
Apple macOS<13.7.6
Apple macOS>=14.0<14.7.6
Apple macOS>=15.0<15.5
Apple tvOS<18.5
Apple visionOS<2.5
Apple WatchOS<11.5
Event History
May 12, 2025
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
DescriptionWeakness
Updated
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Updated
via Apple·12:00 AM
Affected Software
CVE Published
via MITRE·09:42 PM
Data Sourced
via MITRE·09:42 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2025-31246
- CVE-2025-31240
- CVE-2025-31237
- CVE-2025-31251
- CVE-2025-31235
- CVE-2025-31208
- CVE-2025-31196
- CVE-2025-31209
- CVE-2025-31239
- CVE-2025-31233
- CVE-2025-30453
- CVE-2025-24258
- CVE-2025-30448
- CVE-2025-31232
- CVE-2025-24144
- CVE-2025-31219
- CVE-2025-31241
- CVE-2024-8176
- CVE-2025-30440
- CVE-2025-31222
- CVE-2025-24274
- CVE-2025-24142
- CVE-2025-26465
- CVE-2025-26466
- CVE-2025-31245
- CVE-2025-31224
- CVE-2025-31221
- CVE-2025-31213
- CVE-2025-31247
- CVE-2025-30442
- CVE-2025-31242
- CVE-2025-31220
- CVE-2025-24155
- CVE-2025-31212
- CVE-2025-31200
- CVE-2025-31226
- CVE-2025-24224
- CVE-2025-24213
- CVE-2025-31223
- CVE-2025-31238
- CVE-2025-24223
- CVE-2025-31204
- CVE-2025-31217
- CVE-2025-31215
- CVE-2025-31206
- CVE-2025-31205
- CVE-2025-31257
- CVE-2025-43374
- CVE-2025-24097
- CVE-2025-24111
- CVE-2025-31210
- CVE-2025-24225
- CVE-2025-31228
- CVE-2025-24259
- CVE-2025-31216
- CVE-2025-31214
- CVE-2025-31225
- CVE-2025-31253
- CVE-2025-31207
- CVE-2025-31227
- CVE-2025-31234
- CVE-2025-31260
- CVE-2025-24222
- CVE-2025-31236
- CVE-2025-30443
- CVE-2025-31218
- CVE-2025-31256
- CVE-2025-31244
- CVE-2025-31258
- CVE-2025-31266
- CVE-2025-31249
- CVE-2025-31259
- CVE-2025-31250
- CVE-2025-31248
Frequently Asked Questions
1
Is there any workaround for CVE-2025-31208?
No specific workaround for CVE-2025-31208 has been published, and applying the updates remains the recommended approach.