Free tools Windows power users keep installed
One-click scans. No signup required.
PerfektBlue is a real four-vulnerability attack chain in OpenSynergy’s BlueSDK Bluetooth stack. PCA Cyber Security demonstrated remote code execution on specific Volkswagen, Mercedes-Benz, and Škoda infotainment systems, and confirmed part of the exploit chain on tested BMW vehicles. An attacker who is physically close enough to establish the required Bluetooth relationship could potentially access vehicle data, record cabin audio, track location, manipulate infotainment functions, or use the compromised system as a stepping stone toward other vehicle networks.
That does not mean every Volkswagen, Mercedes-Benz, Škoda, or BMW is vulnerable, and the public research did not demonstrate direct control of steering, braking, acceleration, or propulsion. The documented attack is short-range Bluetooth exploitation—not an internet-wide or cellular remote takeover. Vehicle owners should install the latest official infotainment software, ask the manufacturer or dealer whether their specific vehicle is affected, and disable Bluetooth when practical if an update is not immediately available.
What PerfektBlue is
PerfektBlue is the name PCA Cyber Security gave to an exploit chain involving four vulnerabilities in BlueSDK, a closed-source, hardware-agnostic Bluetooth framework developed by OpenSynergy. BlueSDK supports both Bluetooth Classic, formally BR/EDR, and Bluetooth Low Energy. It also implements a wide range of Bluetooth profiles, including profiles used for hands-free calling, media control, and other connected-vehicle functions.
The stack is used particularly in automotive infotainment systems, although PCA warned that other categories of embedded products may also use it. BlueSDK is a framework rather than a single identical product image. Automakers and suppliers can customize its implementation, select different Bluetooth profiles, and apply different security settings. Consequently, finding BlueSDK in a vehicle does not by itself prove that the vehicle has the same vulnerability exposure, pairing requirements, firmware, or exploit path as the systems tested by PCA.
#1 Best Overall
- 【Auto-Precise Alignment Charging】This wireless car charger mount is built-in advanced sensor, just place your phone in after power on, it will adjust your phone in the best charging area while intelligently identify your device and selects optimal charging power performances, greatly improved charging efficiency. Great gift for Christmas!
- 【Upgraded Intelligent Auto-Clamping】The wireless car charger's arms and foot will auto-opening after connecting to power, and will auto clamping firmly once place your phone in, don't need to manually adjust the foot to clamping the phone.
- 【Make Drive Easier】Combines the wireless charger & car phone mount, offers fast charging and saves you from messing with cables while driving. A 360°rotating sphere can help you get the most comfortable and safest GPS Navigation and viewing angle without neck or eye strains while charging your phone.
- 【Secure Stable】The car phone holder mount wireless charging features a strong vent clip and innovative hollow silicone rubber, which can hold your phone without fall off even when driving on bumpy road and will not clamp your phone buttons cause your phone to power off.
- 【FOD Function & Case Friendly】The wireless charging technology and large coil maximize the charging output and efficiency making charging faster than standard car wireless charger. MOKPR car mount wireless charger supports charging through phone cases up to 4mm thick. FOD foreign body detection prevents abnormal charging of equipment, please remove metal/magnetic objects, credit cards or pop holders before charging.
PCA identified potentially affected products using public Bluetooth-certification information and verified the chain on multiple in-vehicle infotainment units. Its public list of affected vendors is explicitly non-exhaustive. The automotive manufacturers publicly named in the research include Mercedes-Benz AG, Volkswagen, Škoda, and BMW.
The four vulnerabilities in the chain
The individual CVEs have different severities and functions. PerfektBlue is significant because the weaknesses can be chained together; they should not be treated as four equally severe, interchangeable bugs.
| CVE | Component and issue | CVSS 3.1 | Why it matters |
|---|---|---|---|
| CVE-2024-45434 | Use-after-free in the AVRCP service | 8.0 high | PCA says this can enable remote code execution in the context of the user running the Bluetooth process. |
| CVE-2024-45431 | Improper validation of a remote L2CAP channel identifier | 3.5 low | It contributes to the attack chain by allowing an attacker to influence channel handling that should be validated. |
| CVE-2024-45433 | RFCOMM control-flow flaw that can bypass a security validation | 5.7 medium | Incoming data can be processed after the relevant validation is bypassed. |
| CVE-2024-45432 | RFCOMM issue involving an incorrect function parameter | 5.7 medium | It can cause unexpected behavior or an information leak and forms part of the broader chain. |
In its advisory, PCA described the overall result as one-click remote code execution on the operating system of a device using BlueSDK. That description needs context: the exact exploit path depends on the device’s firmware, Bluetooth profile configuration, authorization level, and system architecture. The phrase does not mean an attacker can exploit every BlueSDK device from anywhere without proximity or user interaction.
How the Bluetooth attack works in practical terms
PerfektBlue is “remote” in the sense that the attacker does not need physical access to the infotainment unit or a wired diagnostic connection. It is not remote in the sense of an attack launched across the internet.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute- Proximity is required. PCA described Bluetooth communication as generally operating within about 10 meters. Volkswagen described an effective distance of approximately 5 to 7 meters for the vehicle configuration it discussed.
- The attacker must establish the relevant Bluetooth relationship. Depending on the manufacturer’s configuration and the Bluetooth profiles enabled, this may require pairing, authorization, or another security relationship.
- User approval varies by implementation. Some systems may show an on-screen approval request. Others may pair with little or no confirmation, while a particular vulnerable path may be disabled entirely.
- The attacker sends data through the relevant Bluetooth services. The four flaws can then be combined to reach code execution in the Bluetooth process.
- What happens next depends on the vehicle. The attacker receives the permissions of the compromised process unless additional vulnerabilities or privilege-escalation paths are available.
For the Volkswagen configuration publicly described by the company, PCA said exploitation required the ignition to be on, the infotainment system to be in pairing mode, the attacker to remain within roughly 5 to 7 meters, and the driver to approve the external Bluetooth connection on the screen. Those conditions are not universal. BlueSDK customers configure the stack differently, so another vehicle may require less—or more—interaction.
Accordingly, “at most one click” should be read as a statement about user interaction after the attacker is already close to the vehicle and has initiated the Bluetooth exchange. It does not mean zero proximity, universal zero-click exploitation, or an attack that works against every vehicle without the owner noticing anything.
What PCA demonstrated on vehicle systems
The public evidence is strongest for the specific head units and firmware versions that PCA tested. It should not be expanded into a claim that every vehicle in a manufacturer’s fleet is affected.
| Manufacturer and system | Tested configuration | Publicly demonstrated result |
|---|---|---|
| Volkswagen MEB ICAS3 | Used in the ID model line. PCA tested part number 10A035816E with firmware 0792, corresponding to ID software 2.1 and a first-quarter 2021 release, and part number 10A035816J with firmware 0561, corresponding to ID software 3.2.12 and a December 2023 release. | The chain was verified on both firmware versions. PCA obtained a reverse shell on the 0561 version, where the Bluetooth process ran as the sint_sec_btapp user. |
| Mercedes-Benz NTG6 | Head unit part number A 253 900 69 05 / 001, with apilevel/ntg6/080 firmware from approximately 2020–2021. |
PCA demonstrated exploitation. The Bluetooth process ran with phone user permissions. PCA said NTG6 was one of many potentially vulnerable Mercedes-Benz head units. |
| Škoda MIB3 | Part number 3V0035820J with MIB3 0304 firmware from approximately 2022. The unit was installed in the Škoda Superb line and some Volkswagen model lines. | PCA demonstrated exploitation, with the Bluetooth process running as the phone user. |
| BMW Series 2 | BMW 220d and 218i vehicles tested with software updates 07/2024.30 and 03/2024.40. | PCA confirmed part of the chain: an information leak exposing process virtual addresses. The researchers did not complete RCE testing because they lacked the BMW firmware needed for further work. A BMW RCE exploit was considered potentially developable, but it was not publicly demonstrated. |
PCA also said that the newer Mercedes-Benz NTG7 generation may be affected because it uses BlueSDK. That was presented as a possibility, not as a completed public exploit verification. The same distinction applies to other models and head units that may share the software component.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What compromise of the infotainment system could expose
Successful code execution in an infotainment unit can be serious even if the unit is isolated from safety-critical controls. PCA said an attacker could potentially:
Rank #2
- 2-in-1 Mounting for 99% Vehicles: This phone holder for car offers both dashboard and vent mounting options, giving first-time wireless car charger buyers more ways to find the right fit for their vehicle. The military-grade 3M dashboard base uses a dual-support structure and is tested through 4 environmental reliability tests from -40°F to 194°F, while the reinforced vent hook is extended by 60% to fit more air vents. Its compact charging head helps reduce windshield obstruction and avoids blocking airflow, making installation easier and lowering the risk of choosing the wrong mount.
- 15W Wireless Charging for Nonstop Driving: This LISEN MagSafe car mount charger combines a magnetic phone holder and 15W wireless car charger in one compact design, helping keep your phone powered throughout the trip. Just place your phone on the mount when you get in, and charging starts automatically; when you arrive, simply lift it off and go. Built for GPS, calls and music on long drives, it is especially useful for Uber, Lyft and delivery drivers who need steady power on the road. Note: Built-In USB-A May Not Be Enough for 15W Fast Charging. You need a car charger that can provide a charging speed of at least 18W per port.
- Strong Magnetic Hold, No Button Blocking: Built with 24 N52 magnets and up to 3800gf magnetic force, this car phone holder is tested to hold the weight of 8 phones at once for a more stable hold on bumpy roads and sharp turns. Its clamp-free magnetic design keeps side buttons accessible, so you can place your phone with one hand and use GPS, calls or music without extra adjustment.
- Ice Blue LED Glow for Interior Style: This magnetic car accessories mount charger features an ice blue LED light ring that adds a modern accent to your car interior at night. The soft glow helps you quickly locate the mount in low-light driving conditions, while the magnetic one-hand snap-on design makes phone placement easier during night drives, parking, commuting and GPS use.
- Wide Compatibility for Shared Family Cars: This MagSafe car mount charger works with iPhone 18 Pro, iPhone 18 Pro Max and iPhone 17/16/15/14/13/12 series, and also supports Samsung Galaxy S26/S25/S24 and Pixel 10/9 series when paired with a MagSafe-compatible case. Its magnetic alignment helps different phone brands stay securely attached and ready for wireless charging, so families who share one car do not need to switch mounts whenever a different person drives.
- track the vehicle’s GPS coordinates;
- record audio inside the cabin;
- obtain phonebook or other connected-phone information;
- manipulate infotainment functions;
- escalate privileges on the infotainment operating system; and
- attempt lateral movement toward other electronic control units.
A reverse shell or code execution in a Bluetooth process does not automatically provide control over every system in the car. The result depends on the process permissions, operating-system defenses, gateway rules, network segmentation, other vulnerabilities, and the design of the target electronic control units.
Volkswagen said that steering, driver assistance, engine, and braking functions in its architecture were handled by a separate control unit and protected by additional security functions. Security coverage of the research likewise noted that direct control of steering, the horn, or wipers was not demonstrated. The accurate distinction is therefore:
- Confirmed by the research: compromise of specific infotainment systems, including demonstrated RCE on Volkswagen, Mercedes-Benz, and Škoda test units.
- Potential but not established for every vehicle: privilege escalation, movement through vehicle networks, or compromise of other electronic control units.
- Not demonstrated by this research: universal direct control of steering, braking, acceleration, propulsion, or vehicle shutdown.
Does PerfektBlue affect millions of vehicles?
The vulnerability may have broad reach because BlueSDK is a reusable embedded framework and the publicly named vendor list is not exhaustive. However, the public record does not provide a reliable vehicle-by-vehicle count, and it does not establish that millions of vehicles share the same exploitable configuration. A headline claiming that millions of vehicles are definitely exposed is broader than the available evidence supports.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The correct scope is conditional: a vehicle may be exposed if it uses a vulnerable BlueSDK implementation, enables the relevant Bluetooth services, has not received the applicable fix, and meets the attack’s proximity and pairing requirements. Manufacturers may also have disabled a vulnerable path, applied compensating controls, or shipped different firmware.
Disclosure and patch timeline
PCA’s timeline shows why fixing a shared embedded component does not immediately fix every vehicle that contains it:
- May 17, 2024: PCA first contacted OpenSynergy.
- May 24, 2024: After exchanging keys, PCA sent its advisory to OpenSynergy.
- June 12, 2024: OpenSynergy confirmed receipt.
- July 15, 2024: OpenSynergy confirmed the vulnerabilities.
- August 30, 2024: CVE numbers were reserved.
- September 2024: PCA said patches were rolled out to BlueSDK customers.
- October 2024: PCA verified the chain on an additional Škoda infotainment system.
- November 2024: PCA verified it on a Mercedes-Benz system.
- June 2025: PCA tested BMW vehicles and confirmed part of the chain.
- July 7, 2025: PCA published its advisory.
- July 10–11, 2025: Contemporary reporting brought the issue to wider public attention.
PCA said that not all original-equipment manufacturers had received or deployed the patch by June 2025. It attributed some delays to complex vehicle supply chains. PCA also said BMW told researchers in June 2025 that it had not received the vulnerability notice and patch through its supply chain, which is why PCA initially withheld BMW’s name from public disclosure; the later advisory named BMW and documented the partial testing.
Mercedes-Benz told BleepingComputer that it had reviewed the findings, taken necessary mitigation measures, and made a BlueSDK update available through over-the-air updates. Volkswagen said it began investigating impact and remediation after learning of the issue. Those statements do not prove that every potentially affected vehicle in either fleet had been updated at the time of publication.
What vehicle owners should do
1. Install the latest official vehicle software
Check the vehicle’s infotainment settings, connected-car application, owner portal, or manufacturer website for the latest software status. Menu names vary, but a path such as Settings → System → Software update, About, or System information is common. Do not assume that a navigation-map update or phone app update also updates the Bluetooth stack.
Use only the manufacturer’s official over-the-air process or an authorized dealer. A generic software version number is not enough to determine whether the BlueSDK vulnerabilities are fixed, because affected components and patches can differ by head unit, market, model year, and firmware branch.
Rank #3
- [Innovative Arch-Bridge Flexible Base] Engineered for ultimate versatility, our arch-bridge adhesive base is crafted from premium flexible material that contours perfectly to curved, uneven, or complex dashboards. Unlike rigid mounts, this unique design provides a massive contact area, ensuring a rock-solid grip in any position of your car. Tips: For maximum adhesion, clean the surface thoroughly and allow the heavy-duty adhesive to cure for 24 hours before first use
- [Versatile 2-in-1 Mounting System] This premium car holder offers dual-mounting options to perfectly suit your vehicle's interior. You can use the innovative arch-bridge adhesive base for a customized, rock-solid fit on any dashboard surface, or switch to the upgraded metal hook air vent clip for a compact setup. The metal hook securely "locks" onto most horizontal and vertical vent blades, ensuring it never falls off. Combined with a 360° flexible ball joint, you can effortlessly adjust for a distraction-free driving experience
- [15W Fast Wireless Charging & Thermal Safety] Experience rapid energy recovery with our 15W wireless car charger, optimized for high-efficiency power delivery during navigation. This set includes a high-quality 3FT USB C to USB C cable to ensure a stable, fast connection. Built-in smart-chip technology provides over-temperature protection, keeping your phone battery healthy and safe.(⚠️ Note: To achieve optimal 15W fast charging, pairing with a QC3.0 or PD 18W+ car charger adapter is strictly required)
- [Military-Grade N55 Magnets - 2800gf Power] Equipped with a powerful ring of 25 upgraded N55 magnets, this magnetic car mount provides an industry-leading 2800gf (6.2lbs) of magnetic holding force. It keeps your device absolutely steady even on the most bumpy roads or during sharp turns. The precise magnetic alignment allows for an instant "Snap & Go" experience—simply place your phone and drive without fumbling with clamps
- [Universal MagSafe Compatibility & Included Ring] Tailor-made to be compatible with iPhone 17/16/15/14/13/12 Series. For Samsung, Pixel, or older iPhones, and other wireless-charging-enabled smartphones, simply attach the included magnetic ring to your phone or smooth case for a seamless snap-and-charge experience. ⚠️ Important Note: To ensure the strongest magnetic grip and optimal charging speed, please use a bare phone, an official MagSafe case, or a slim magnetic case. It is NOT compatible with non-magnetic thick cases, wallet cases, or pop grips
2. Ask the manufacturer a vehicle-specific question
Contact the automaker’s support channel or dealer and provide the vehicle identification number, model year, market, and current infotainment software version. Ask:
- Does this VIN or head-unit part number use OpenSynergy BlueSDK?
- Is the installed Bluetooth stack affected by CVE-2024-45431, CVE-2024-45432, CVE-2024-45433, or CVE-2024-45434?
- Has the relevant fix been installed, or is an over-the-air or dealer update required?
- What software version confirms remediation for this exact vehicle?
If the automaker offers manufacturer infotainment update support, ask the provider to confirm completion rather than relying only on the fact that an update was offered. There is no complete public vehicle-by-vehicle remediation inventory, so the manufacturer is the appropriate source for VIN-specific status.
3. Disable Bluetooth temporarily if updating is not possible
PCA recommends disabling Bluetooth entirely when an update is not immediately available or Bluetooth is not needed. This can affect hands-free calling, wireless media, digital-key features, and other connected-car functions, but it removes the documented Bluetooth route while it is disabled.
Turning off pairing mode or deleting a single phone is not necessarily equivalent to disabling Bluetooth. The exact control varies by vehicle. If the infotainment system cannot fully disable Bluetooth, keep the vehicle out of discoverable or pairing mode where possible and ask the manufacturer for the recommended temporary mitigation.
4. Do not mistake consumer accessories for a software fix
A generic OBD2 code reader, Bluetooth scanner, privacy accessory, or phone-security application cannot be assumed to detect or repair PerfektBlue. The issue is in an embedded Bluetooth implementation inside the infotainment system, not a conventional engine diagnostic trouble code. An OBD2 scanner is not a BlueSDK vulnerability scanner, and a physical privacy accessory does not patch software or prevent a vulnerable Bluetooth process from executing code.
5. Treat unexplained Bluetooth prompts seriously
Do not approve an unfamiliar pairing request. This is useful basic hygiene, but it is not a complete defense because some vehicle configurations may pair with little or no confirmation. Owners should prioritize an official software update or manufacturer confirmation rather than relying on user vigilance alone.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What automakers and suppliers should learn from PerfektBlue
PerfektBlue is not only a coding flaw; it is also a software-inventory and patch-distribution problem. A supplier may repair a shared component, but the fix still has to be identified, integrated, tested, approved, and delivered across multiple vehicle programs and model years.
Automakers, tier-one suppliers, fleet operators, and connected-vehicle integrators should consider:
- Maintaining an accurate software-component inventory and SBOM: teams need to know which vehicles and head units contain BlueSDK, which version is present, and which Bluetooth profiles are enabled.
- Coordinating vulnerability response across the supply chain: notification must reach the right OEM, supplier, regional organization, and update team without depending on informal channels.
- Supporting secure over-the-air updates: a patch that cannot be distributed quickly leaves a known attack surface in the field.
- Testing customized implementations: Bluetooth protocol fuzzing, binary analysis, and security review should cover the vendor-specific configuration rather than assuming the upstream framework behaves identically everywhere.
- Strengthening segmentation: infotainment compromise should not become a straightforward route into safety-critical electronic control units.
- Verifying remediation: update campaigns need completion tracking and a way to confirm the actual software state of each affected vehicle.
For organizations responsible for connected-vehicle programs, an automotive cybersecurity assessment that combines component inventory, firmware analysis, Bluetooth testing, update verification, and network-segmentation review is more relevant than a generic consumer antivirus product or an ordinary diagnostic scanner.
Rank #4
- 【3-in-1 & Flexible Viewing Angle】You have multiple installation of the car phone holder,it can be installed on the windshield, dashboard,air vent and table securely, and is ideal for cars, trucks, SUVs, etc. This phone holders for your car with a 360-degree rotating and pivoting ball joint that can help you get the most comfortable and safest viewing without neck or eye strain while charging your phone. [ NOTE: Not compatible with Foldable Phone for charging ]
- 【Latest Chip for More Efficient Charging】The MOKPR Wireless Car Charger is a built-in advanced sensor, just place your phone in after power on, it will intelligent identify your phone and Auto-adjusting phone to the best charging area and fast charge.
- 【Automatic Precise Alignment】The car phone mount's arms and foot will auto-opening after connecting to power, and will auto clamping firmly once place your phone inside, then it will intelligent identify and auto-adjusting the phone to the best charging area according to your phone model, don't need to manually adjust the foot to clamping the phone.
- 【Case Friendly & FOD FUNCTION】This wireless charger supports charging through phone cases up to 4mm thick.FOD foreign body detection prevents abnormal charging of equipment, please remove metal/magnetic objects, credit cards or pop holders before charging.
- 【Strong Suction Cup & Secure Stable Install】This phone holder features an extra-strong suction cup, it easily sticks securely on the dashboard or most flat surfaces. Even if driving on a bumpy road, you don’t need to worry about it falling off.
What the public evidence does—and does not—show
The strongest supported conclusion is that PerfektBlue exposed a meaningful Bluetooth attack surface in vehicle infotainment systems using OpenSynergy BlueSDK. PCA demonstrated RCE on three named automotive infotainment platforms and partial exploit-chain impact on BMW vehicles.
Recommended Free Tools
The evidence does not support these broader claims:
- that all vehicles from the named manufacturers are vulnerable;
- that every BlueSDK implementation has the same pairing requirements;
- that the attack works over the internet or cellular networks;
- that all exploitation is zero-click;
- that every affected vehicle has already been patched; or
- that PerfektBlue directly controls steering, braking, acceleration, or propulsion.
Owners should take the issue seriously because infotainment compromise can expose location, phone, and cabin data and may create a platform for further attacks. They should also avoid panic: the public research describes a close-range, configuration-dependent attack against particular software implementations, not a universal takeover of every connected car.
Frequently Asked Questions
Can PerfektBlue let an attacker steal or drive my car?
The research demonstrated code execution on specific infotainment systems, not universal control of a vehicle’s steering, brakes, acceleration, or propulsion. An attacker could potentially access infotainment-connected data and attempt lateral movement, but downstream impact depends on each vehicle’s network segmentation, gateway controls, permissions, and other vulnerabilities.
Is my Volkswagen, Mercedes-Benz, Škoda, or BMW automatically vulnerable?
No. The public tests covered particular head units, firmware versions, and vehicle configurations. The affected-vendor list is non-exhaustive, and manufacturers can customize BlueSDK or disable relevant Bluetooth paths. Ask the manufacturer or dealer to check the VIN, head-unit part number, and software version.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Does deleting my phone from the vehicle fix PerfektBlue?
No. Removing a paired phone may reduce ordinary pairing exposure, but it is not the same as patching the infotainment Bluetooth stack or disabling Bluetooth. Install the official update, and disable Bluetooth temporarily if the manufacturer recommends it and an update is not available.
Can an OBD2 scanner check whether my vehicle has PerfektBlue?
No generic OBD2 code reader should be described as a PerfektBlue detector or fix. PerfektBlue concerns an embedded Bluetooth implementation in the infotainment system, while ordinary OBD2 scanners read vehicle diagnostic data. Manufacturer software records and VIN-specific support are the appropriate sources for remediation status.
The Bottom Line
PerfektBlue is a serious but conditional Bluetooth risk. PCA proved remote code execution on specific Volkswagen, Mercedes-Benz, and Škoda infotainment platforms and confirmed a partial exploit-chain effect on BMW test vehicles. The attack requires close-range Bluetooth access and implementation-dependent pairing or authorization; it is not an internet-wide car takeover.
Update the vehicle through official channels, obtain VIN-specific confirmation from the manufacturer or dealer, and disable Bluetooth when practical until the vehicle’s status is known. Do not claim that every named vehicle is vulnerable—or that the research proved direct control of steering and brakes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
