Is using Linq to SQL in a MembershipProvider implementation safe?

I'm creating a custom MembershipProvider for开发者_StackOverflow中文版 an ASP.NET MVC website, and I was planning on using LINQ to SQL for the internals, as I am for the rest of the website. Are there any issues with this, specifically any security issues it causes?

Linq-To-SQL prevents SQL injection attacks; so any potential holes would normally be the result of logical errors created in the customer membership provider.

Depending on your implementation there should be no more of a security risk than writing the calls in TSQL or stored procedures.