The U.S. Is Restricting Chinese- and Russian-Linked Self-Driving Software—What the Rule Actually Does

Short answer: The United States did not impose a blanket ban on every Chinese-developed self-driving system. A restriction first reported as a proposed China-focused measure in 2024 became a final connected-vehicle rule covering certain software and hardware linked to China or Russia. It can block specified imports, U.S. sales, vehicle integrations, and—in some cases—commercial autonomous-driving services such as robotaxis.

The rule is aimed primarily at manufacturers, importers, software integrators, and operators. It does not order people who already own cars to uninstall software or stop driving. Its application depends on the vehicle category, the software’s function, its origin and ownership, continuing maintenance rights, and the transaction involved.

#	Preview	Product	Price
1		galphi 4K Dash Cam Front, 5GHz WiFi, 32GB Card Included, Mini Dashcam	$55.99	Buy on Amazon
2		1080P Dual Dash Camera for Car Front and Inside Dashcam Car Security Video Recorder,170°Wide Angle...	$15.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

How the headline changed

The headline “the U.S. will ban Chinese self-driving software” originated with August 2024 reporting about a planned Commerce Department restriction. That proposal emerged after the Biden administration opened a national-security inquiry into connected vehicles in February 2024. Commerce cited concerns that connected vehicles could collect sensitive data, communicate with infrastructure, or potentially be remotely manipulated or disabled. Commerce’s announcement described an inquiry and possible action—not an immediate ban on every Chinese autonomous-driving product.

The later final rule is more precise and broader in one respect: it covers Russia as well as China. It is also narrower than the shorthand suggests because it regulates defined transactions involving covered connected vehicles, vehicle-connectivity-system hardware, and covered software.

#1 Best Overall

galphi 4K Dash Cam Front, 5GHz WiFi, 32GB Card Included, Mini Dashcam

• 💖💖【Important Note】Due to soaring memory chip costs, many brands have eliminated memory cards entirely, requiring a separate purchase. However, to save you the hassle of buying extra accessories, we are resisting cost pressures without raising our dashcam's price. Starting June 26, 2026, this camera will include a 32GB memory card (previously 64GB) so you can still use it out of the box. For extended storage, we highly recommend purchasing a Class 10, U3, and V30 (or higher) memory card.
• 【4K 2160P Resolution Dash Cam】Capture every drive in stunning 4K UHD resolution with the Galphi front dash cam, featuring a 160-degree wide-angle lens for clear, cinematic video footage. Ideal for family cars, new drivers, and Uber/Lyft drivers, it provides reliable video evidence for accident disputes and insurance claims.
• 【Advanced 5GHz WiFi with App】 Featuring cutting-edge 5GHz WiFi and a free app, the video download speed reaches up to 8MB/s, compared to just 2MB/s with the 2.4GHz option. This greatly reduces download times and minimizes lag during video playback.
• 【No Screen & Less Distraction】This dash camerma features a screen-free design, minimizing distractions while you drive so you can stay focused on the road. Enjoy peace of mind knowing your camera is recording without taking your attention away from the journey.
• 【Compact and Super Easy to Install】The dash cam's slim and compact design ensures it won't obstruct your view. With easy installation and clear, detailed instructions included, even first-time users can set it up without any hassle.

$55.99

Buy on Amazon

That distinction matters. “Developed in China” is not the legal test by itself, and “self-driving” is not a sufficiently precise regulatory category.

What the final rule restricts

The final Bureau of Industry and Security rule creates several related restrictions for covered connected vehicles:

• VCS hardware imports: A vehicle-connectivity-system hardware importer generally may not knowingly import covered hardware linked to China or Russia.
• Completed-vehicle imports: A connected-vehicle manufacturer generally may not knowingly import completed connected vehicles containing covered China- or Russia-linked software.
• U.S. sales: A connected-vehicle manufacturer generally may not knowingly sell covered completed connected vehicles containing prohibited software in the United States.
• Foreign-adversary-controlled manufacturers: A manufacturer owned by, controlled by, or subject to the jurisdiction or direction of China or Russia may face restrictions even when the relevant hardware or software does not itself originate in one of those countries.
• Commercial autonomous services: Certain foreign-adversary-controlled manufacturers may also be barred from providing U.S. commercial services using completed connected vehicles equipped with automated-driving systems. That can include robotaxi or rideshare operations.

The controlling text is the final connected-vehicle rule. The restrictions are transaction-specific; they are not a general instruction that every Chinese autonomous vehicle must be removed from U.S. roads.

Is Chinese-developed software automatically illegal?

No. The rule examines whether covered software was designed, developed, manufactured, or supplied by a person or entity owned by, controlled by, or subject to the jurisdiction or direction of China or Russia. Continuing rights can also matter, including licensing, servicing, maintenance, and software-update responsibilities.

A software stack assembled outside China can still raise compliance issues if a China- or Russia-linked entity retains relevant rights or supplies a covered component. Conversely, the mere fact that an individual engineer is a Chinese or Russian citizen does not automatically make software prohibited when that person works outside the country for an entity not controlled by its government.

BIS also explained that a covered software subcomponent incorporated into a larger automated-driving software suite may cause the broader suite to be treated as covered. That makes ordinary labels such as “U.S. software” or “foreign supplier” inadequate for serious compliance work.

What software is covered?

The rule focuses on software that directly enables or supports covered vehicle-connectivity-system or automated-driving-system functions.

For an automated-driving system, the relevant functions generally include software that:

• Processes sensor and vehicle data;
• Perceives and classifies objects;
• Makes driving decisions; and
• Controls or executes autonomous vehicle behavior.

BIS deliberately focused on ADS software rather than automatically prohibiting every piece of autonomous-driving hardware. LiDAR, cameras, sensors, electronic control units, and other hardware are not prohibited merely because they support an automated-driving system. VCS hardware is treated separately under the rule.

The analysis can still involve middleware, drivers, firmware, third-party libraries, cloud-connected update systems, maintenance contracts, and joint-venture arrangements. The location of a cloud server alone does not decide whether vehicle-control software is covered.

ADS is not the same as ADAS

One of the most important corrections to the 2024 coverage is the difference between an automated-driving system (ADS) and an advanced driver-assistance system (ADAS).

The original reporting emphasized Level 3 and higher automated-driving systems. The final rule does not simply prohibit everything labeled “Level 3 and above.” Instead, it uses regulatory definitions tied to the system’s actual functions and the SAE driving-automation framework.

A system marketed as “hands-free,” “automated,” or “self-driving” may still legally be Level 2 assistance. But companies should not assume that every Level 2 product is exempt without reviewing its actual functions. Borderline cases can be submitted to BIS for an advisory opinion.

Which vehicles and businesses are affected?

Passenger vehicles and covered connected vehicles

The rule primarily addresses covered connected vehicles manufactured or sold for use on public roads, with particular importance for passenger vehicles and vehicles below the applicable commercial-vehicle threshold. The exact vehicle definitions, weight limits, model years, and transaction dates control the result.

BIS stated that the commercial-vehicle sector was outside this rulemaking and that a separate proposal may address that sector. The rule therefore should not casually be described as covering heavy trucks, buses, and every commercial fleet.

Automakers and importers

A connected-vehicle manufacturer can include a U.S. person that manufactures or assembles completed connected vehicles in the United States for U.S. sale, imports connected vehicles for U.S. sale, or integrates ADS software into a completed connected vehicle for U.S. sale.

That last category is significant. An aftermarket or robotaxi company cannot necessarily avoid the rule by buying a finished vehicle and installing an autonomous-driving stack later. BIS treats ADS integration as a manufacturing operation for the rule’s purposes.

Robotaxi and rideshare operators

The commercial-service provision gives the rule consequences beyond vehicle sales. A foreign-adversary-controlled manufacturer that integrates ADS into completed connected vehicles and operates those vehicles commercially in the United States may face restrictions on robotaxi or rideshare services.

This does not mean every robotaxi company is banned, nor does it establish that any particular named company violates the rule. The outcome depends on control, vehicle status, software provenance, integration, and the specific U.S. service.

Why the U.S. adopted the restrictions

Commerce and BIS describe connected vehicles as mobile data and communications platforms. Their stated concerns include:

• Collection of location, personal, and operational data;
• Connections to telecommunications networks, other vehicles, the electric grid, and infrastructure;
• Remote access, manipulation, or disabling;
• Malicious alteration of sensor inputs or autonomous-driving decisions;
• Software vulnerabilities or backdoors; and
• Government influence over companies operating under Chinese or Russian jurisdiction.

These are the government’s national-security and cybersecurity justifications for the rule. They should not be converted into a claim that every Chinese-developed system has been proven to contain malicious code. The rule is a risk-management and market-access measure, not a finding that every affected product is demonstrably compromised.

Important exclusions and limits

Nationality alone is not enough

An employee’s or contractor’s Chinese or Russian citizenship does not automatically make a software product covered. The rule looks at the relevant entity, its control and jurisdiction, and the software relationship—not nationality in isolation.

Open-source code can receive limited treatment

Open-source software with fully available human-readable source code is excluded in specified circumstances unless it is modified for proprietary purposes and not redistributed or shared. Companies must examine how the code is used rather than assume that calling a component “open source” resolves the issue.

Rank #2

1080P Dual Dash Camera for Car Front and Inside Dashcam Car Security Video Recorder,170°Wide Angle Vehicle Cam,WDR,G-Sensor,Loop Recording,Night Vision (Dual Dash Cam Without Card)

• 【1080P Front and Inside Dash Cam 】Super Clear 1920*1080P pictures can be provided by the small cam. The car camera can reocrd videos front and inside of the car at the same time.
• 【 Dash Camers for Car Easy Installation】Just install the dashcam on the windshield, then plug the power cable into the car cigarette lighters. Please clean the windshield, so the sunction cup can be fixed tightly on the windshield.
• 【 Dash Cam Front and Inside Built-in G-sensor】If the dash camera detects a sudden shake/collision, it will lock the related video. So the important video will not be overwritten. Accident scene can be truly restored. This locked video will not be re-written even SD card is full.
• 【 Loop Recording with Night Vision】 The SD Card will start to record automatically when car started on. If SD Card is recorded full, the newest video will recover the oldest video. And the night vision sensor strats to work in the night.
• 【Suitable for Various Cars】This car das cam is suitable for kinds of cars, like vehicle, truck, bus and farm harvester.

$15.99

Buy on Amazon

Legacy code is not universally grandfathered

The rule contains treatment for certain older software components. Components designed, developed, manufactured, or supplied before March 17, 2026 may qualify for an exclusion if they are not later maintained, augmented, or otherwise altered by a covered China- or Russia-linked entity.

This is not a blanket exemption for every existing vehicle or software stack. Continuing maintenance, updates, modifications, and contractual rights matter.

ADS-supporting hardware is not automatically prohibited

Hardware used to support autonomous driving is not automatically banned merely because it is linked to China or Russia. The rule prioritizes ADS software while separately regulating covered VCS hardware. That distinction does not eliminate supply-chain scrutiny, but it prevents the inaccurate conclusion that every Chinese sensor or computing component is prohibited.

Minority investment is not automatically control

A foreign shareholder’s minority public-company stake does not necessarily trigger the rule if it comes without control, management rights, or a board seat. Ownership and control must be evaluated under the rule’s definitions and the facts of the relationship.

Key dates

How manufacturers must demonstrate compliance

The final rule provides several compliance mechanisms, including Declarations of Conformity, general authorizations, specific authorizations, advisory opinions, and limited exceptions.

Declarations of Conformity

A Declaration of Conformity requires the relevant importer or manufacturer to certify that covered software or VCS hardware does not fall within the prohibited China- or Russia-linked category. The company must maintain supporting due-diligence records.

Those records may include:

• Company identity and contact information;
• Vehicle make, model, trim, and VIN-series information;
• Certification about software design, development, manufacture, and supply;
• Supplier declarations and contractual guarantees;
• Technical and provenance records;
• Hardware bills of materials, or HBOMs; and
• Potential third-party assessments.

The rule specifically discusses HBOMs as records of hardware supply-chain relationships, including manufacturers and related firmware. A company will also need software bills of materials, source-code provenance, update histories, and licensing records in practice, although the rule does not create one universal software-bill-of-materials format.

Authorizations and advisory opinions

Companies can use general or specific authorization processes where available. They may also request an advisory opinion from BIS when the application of the rule is unclear.

Authorization is not automatic. A rule that permits companies to apply for authorization does not prove that a particular company has received one. Specific authorizations may not be publicly disclosed, so outsiders cannot necessarily assemble a complete public list of beneficiaries.

Limited exceptions

The rule includes limited exceptions relating to circumstances such as force-majeure events, supply-chain disruption, corporate transactions, facility relocation, and certain vehicles already being imported or sold at the effective date. These are narrow provisions, not a universal exemption from compliance.

A practical compliance checklist

1. Classify the vehicle. Determine whether it is a covered connected vehicle and whether passenger-vehicle, weight, model-year, or commercial-vehicle exclusions apply.
2. Classify the technology. Separate VCS hardware, ADS software, ADAS software, firmware, middleware, drivers, and unrelated vehicle systems.
3. Map the functions. Identify whether each software component processes sensor data, perceives objects, makes driving decisions, or controls vehicle behavior.
4. Trace provenance. Identify who designed, developed, manufactured, and supplied every relevant component.
5. Review control and ownership. Examine subsidiaries, joint ventures, board rights, government influence, licensing, servicing, maintenance, and update obligations.
6. Check dates. Determine when each component was created and whether it was modified or maintained after the relevant legacy-code cutoff.
7. Identify the transaction. Import, U.S. sale, ADS integration, and commercial autonomous service can create different obligations.
8. Document the result. Prepare declarations, supplier records, HBOMs, software provenance records, and due-diligence evidence.
9. Escalate uncertainty. Seek an authorization or BIS advisory opinion rather than relying on marketing terminology or an informal supplier assurance.

What this means for automakers and suppliers

The main business effect is a more demanding software and hardware supply-chain review. Automakers and technology suppliers may need to:

• Audit code origin, ownership, maintenance, and licensing;
• Obtain stronger supplier representations and technical records;
• Reassign development or maintenance work;
• Remove or redesign China- or Russia-linked modules;
• Track third-party libraries, firmware, middleware, and update systems;
• Delay vehicle launches or autonomous-service expansion while compliance is assessed; and
• Bear additional engineering, legal, cybersecurity, and documentation costs.

BIS recognized that tracing mature codebases and avoiding supply-chain disruption could be burdensome. The legacy-code treatment and authorization mechanisms are intended to reduce some of that burden, but they do not make globally distributed software easy to classify.

The core trade-off is straightforward: the government is accepting additional compliance cost and possible technology disruption to reduce perceived national-security and data-security exposure. The rule’s decision to focus on ADS software rather than all ADS hardware reflects an attempt to target the functions viewed as most sensitive without prohibiting every component in an autonomous-driving stack.

What it means for U.S. consumers

For most drivers, this is a manufacturer and operator rule, not a vehicle-owner rule.

• It does not tell current owners to remove Chinese software.
• It does not require people to stop driving vehicles they already own.
• It may affect which new vehicles and autonomous-driving options can be sold or launched in the United States.
• It may affect whether particular robotaxi or autonomous rideshare services can operate.
• It could reduce the number of eligible technology suppliers and increase development costs.

There is no reliable basis for assigning a specific percentage increase to vehicle prices. Any consumer-price effect will depend on redesign costs, supplier alternatives, launch decisions, and competition.

A vehicle’s brand nationality is also not enough to determine coverage. The relevant questions concern the vehicle category, software functions, supplier relationships, ownership and control, maintenance rights, and the transaction taking place.

What remains fact-specific

The rule does not provide a simple public list of every affected vehicle, software package, or company. Important questions can depend on confidential supply-chain and contract information, including:

• Whether a mixed-origin software suite contains a covered component;
• Whether middleware or firmware directly supports a covered vehicle function;
• Who retains maintenance, update, licensing, or intellectual-property rights;
• Whether a borderline system is ADAS or ADS under the definitions;
• Whether an aftermarket integration is treated as manufacturing;
• How a particular ownership structure affects foreign-adversary control;
• Whether a commercial vehicle falls inside a future rule rather than this one; and
• Whether a company has received a nonpublic specific authorization.

That uncertainty is why claims that “all Chinese autonomous vehicles are banned,” “all Level 2 systems are exempt,” or “every existing car is grandfathered” are unreliable.

Quick Recap

Bestseller No. 1

galphi 4K Dash Cam Front, 5GHz WiFi, 32GB Card Included, Mini Dashcam

$55.99

Bestseller No. 2

1080P Dual Dash Camera for Car Front and Inside Dashcam Car Security Video Recorder,170°Wide Angle Vehicle Cam,WDR,G-Sensor,Loop Recording,Night Vision (Dual Dash Cam Without Card)

$15.99

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.